Hector Jones
asked on
Outlook 2016 will not connect to Exchange 2016 following SSL install
We have a new build Exchange 2016 server (on Server 2012 R2) and several Outlook 2016 clients. When we attempted to connect the clients with the default settings on Exchange (no SSL added, namespaces not changed etc.), apart from a certificate error which we could ok to continue, the clients connected properly.
Today, we added a GoDaddy SSL and changed all our namespaces to the external address e.g. office.domain.com. Now, the clients still give the certificate error but they also won't connect to Exchange with the error :
The action cannot be completed the connection to Microsoft exchange is unavailable outlook must be online or connected to complete this action.
We have an identical setup in two other offices (none are linked) and they work perfectly with the same settings. We have double checked their namespaces, DNS, IIS bindings and run Outlook test settings, but nothing will make these clients connect. The only difference is the faulty office is using Cumulative Update 2.
I'm slowly going insane here so would greatly appreciate any help to resolve this. I have tried rolling one client back to Office 2013 but get the same error.
Today, we added a GoDaddy SSL and changed all our namespaces to the external address e.g. office.domain.com. Now, the clients still give the certificate error but they also won't connect to Exchange with the error :
The action cannot be completed the connection to Microsoft exchange is unavailable outlook must be online or connected to complete this action.
We have an identical setup in two other offices (none are linked) and they work perfectly with the same settings. We have double checked their namespaces, DNS, IIS bindings and run Outlook test settings, but nothing will make these clients connect. The only difference is the faulty office is using Cumulative Update 2.
I'm slowly going insane here so would greatly appreciate any help to resolve this. I have tried rolling one client back to Office 2013 but get the same error.
Last Comment
Oh, and if you've done all that then just create a new Outlook profile for the affected systems.
ASKER
Thanks Jeffrey, I've run the Outlook Test email configuration and it all looks correct and (apart from unique office name of course), completely matches the other two offices configuration.
I've also tried creating new profiles but get exactly the same error on all the machines.
I've just re-checked all namespaces, both via the gui and PowerShell and everything is exactly as it should and have triple checked DNS can resolve both internally and externally.
I actually wish I could find an error somewhere to fix, but these clients just will not connect.
I've also tried creating new profiles but get exactly the same error on all the machines.
I've just re-checked all namespaces, both via the gui and PowerShell and everything is exactly as it should and have triple checked DNS can resolve both internally and externally.
I actually wish I could find an error somewhere to fix, but these clients just will not connect.
Then your next step is to download and run the Microsoft Connectivity Analyzer Tool found here: https://testconnectivity.microsoft.com (on the "Client" tab)
Try restarting the Autodiscover App Pool on the Exchange server where the mailbox resides; or restart the server if you haven't already.
https://oddytee.wordpress.com/2016/08/16/outlook-client-does-not-connect-to-mailbox-on-exchange-2016/
https://oddytee.wordpress.com/2016/08/16/outlook-client-does-not-connect-to-mailbox-on-exchange-2016/
ASKER
Thanks again for the help.
The server has been restarted and I've restarted the Autodiscover pool, no change. These are all new mailboxes on a new server although we did pst mailboxes over via Outlook from our old SBS2008 server.
I ran the Analyzer from the Client tab and it fails on AutoDiscovery connectivity. Everything else it passes. Looking at the failure though, it is looking just at domain.com but our namespace uses office.domain.com. Is the Analyzer confused or have I missed something ?
I've also just run the Analyzer on a client pc in another office that works perfectly and get the same failure, again it seems to look at domain.com not office.domain.com.
The server has been restarted and I've restarted the Autodiscover pool, no change. These are all new mailboxes on a new server although we did pst mailboxes over via Outlook from our old SBS2008 server.
I ran the Analyzer from the Client tab and it fails on AutoDiscovery connectivity. Everything else it passes. Looking at the failure though, it is looking just at domain.com but our namespace uses office.domain.com. Is the Analyzer confused or have I missed something ?
I've also just run the Analyzer on a client pc in another office that works perfectly and get the same failure, again it seems to look at domain.com not office.domain.com.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Resolved by Microsoft support.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
To troubleshoot, from a workstation you can hold CTRL down and right click the Outlook icon in the status area of the taskbar to select "Test e-mail autoconfiguration" and it will step through what Outlook is seeing as it tries to connect.