Solved

Outlook 2016 will not connect to Exchange 2016 following SSL install

Posted on 2016-09-03
8
45 Views
Last Modified: 2016-09-10
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.
0
Comment
Question by:Hector Jones
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
8 Comments
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 41783271
Outlook 2016 uses only Autodiscover to connect to an Exchange Server.  If you've created a Forward Lookup Zone for your external domain in your Windows DNS, you need to be sure you also have the proper autodiscover record included (generally just a cname record which points autodiscover to server.domain.com).

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.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 41783272
Oh, and if you've done all that then just create a new Outlook profile for the affected systems.
0
 

Author Comment

by:Hector Jones
ID: 41783276
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.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 41783296
Then your next step is to download and run the Microsoft Connectivity Analyzer Tool found here:  https://testconnectivity.microsoft.com (on the "Client" tab)
0
 
LVL 15

Expert Comment

by:Todd Nelson
ID: 41783307
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/
0
 

Author Comment

by:Hector Jones
ID: 41783434
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.
0
 

Accepted Solution

by:
Hector Jones earned 0 total points
ID: 41784620
An update to this, I raised a support call with Microsoft and the problem was that IIS authentication was completely blank, something he had never seen before. He restored that and everything works perfectly now.
0
 

Author Closing Comment

by:Hector Jones
ID: 41792496
Resolved by Microsoft support.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this step by step procedure, you will come to know the details of creating an Outlook meeting in 2007, 2010, 2013 & 2016.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question