loosain
asked on
outlook 2016 asks for credentials
We are using exchange with outlook 2016 and been asked for credentials since yesterday.
It seems that the used mailadress in outlook is also registered at office.com for some reason.
After entering the password from office.com the login-mask from outlook won't return but outlook still says that it is not connected to exchange. After clicking the information at the bottom it changes immediatly to "online with exchange".
We also updated our office to the newest version, but the error ist still there.
Restarting doesn't solved the problem, either. And therefore the starting process last at least 5 minutes.
It seems that outlook looks somewhere for my account but can't find any.
Can any proof this behaviour or solve?
Regards
Jens
It seems that the used mailadress in outlook is also registered at office.com for some reason.
After entering the password from office.com the login-mask from outlook won't return but outlook still says that it is not connected to exchange. After clicking the information at the bottom it changes immediatly to "online with exchange".
We also updated our office to the newest version, but the error ist still there.
Restarting doesn't solved the problem, either. And therefore the starting process last at least 5 minutes.
It seems that outlook looks somewhere for my account but can't find any.
Can any proof this behaviour or solve?
Regards
Jens
ASKER
autodiscover is working and pointing to on premise server. Only some workstations are asking for the credentials. Not all clients have the Problem, so dns and server settings shouldn´t be the problem... It must have been something with the client.
We are seeing this also. We believe it's due to a Microsoft update. It only affects Outlook 2016. For some reason the Outlook client is trying to authenticate against "outlook.office365.com" (which you'll see if you look in the cached credentials list on the client) when the email account is hosted on an on-premises Exchange server (Exchange 2013 or 2016).
The only solution we have found so far is to uninstall Office 2016, then reinstall it and decline any updates.
The only solution we have found so far is to uninstall Office 2016, then reinstall it and decline any updates.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This fix listed in my post above worked for us.
ASKER
We found out that it obviously is a problem eith the newest update. We found another way to go back in the update-path:
cd %programfiles%
cd "microsoft shared"
cd clickdown
OfficeC2RClient.exe /update user updatetoversion=16.0.8326. 2107
cd %programfiles%
cd "microsoft shared"
cd clickdown
OfficeC2RClient.exe /update user updatetoversion=16.0.8326.
For internal clients if you have a windows domain simply setup an SRV record Exchange AutoDiscover Errors – Creating an AutoDiscover SRV Record
Pete