J4sstrom
asked on
Cannot connect one particular user to Exchange 2013 via Outlook 2016
I have two new Windows 10 boxes pre-loaded with Office 2016. All seemed well during setup until opening Outlook. On Box A, I can connect user to Exchange with no issue. On Box B, I get a message that there is no connectivity to Exchange. I can connect to the account in question via Outlook 2013 and OWA, just not in 2016.
I thought since so early in setup stage, maybe just switch user logins on the boxes and move forward. Well, the account on Box A works fine on Box B for Outlook, but the account on Box B gets the same connectivity error on Box A.
Sounds like something a setting on Exchange, but nobody has touched it in weeks.
Thoughts?
I thought since so early in setup stage, maybe just switch user logins on the boxes and move forward. Well, the account on Box A works fine on Box B for Outlook, but the account on Box B gets the same connectivity error on Box A.
Sounds like something a setting on Exchange, but nobody has touched it in weeks.
Thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Seems a reboot of server straightened it out?
Yes, that should have been one of first things to do, but it wasn't.
Yes, that should have been one of first things to do, but it wasn't.
Fixing permissions shouldn't require a reboot, but I could see how the combination would fix things, or just a reboot itself...
As to that being one of the first things to do, in desktops, yes, that's true, but with servers it's one of the last things you want to do. I always say, the main difference between desktop support and server support is that you have to fix what's wrong with the server without even thinking about rebooting as a troubleshooting step.
As to that being one of the first things to do, in desktops, yes, that's true, but with servers it's one of the last things you want to do. I always say, the main difference between desktop support and server support is that you have to fix what's wrong with the server without even thinking about rebooting as a troubleshooting step.
ASKER