I'm dealing with a frustrating issue where my Outlook 2010 just won't connect to Exchange 2013 after I renewed the SSL certificate. I've got everything set up on Exchange Server 2013 CU23 running on Windows Server 2012 R2, and the clients are on Windows 7 with Outlook 2010. Unfortunately, OWA and ECP are not accessible due to setup design, so I'm focusing on getting Outlook to work again. The specific error I keep getting is, "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable."
I've already installed the new DigiCert certificate and bound it to IIS for HTTPS, plus I've done a lot of troubleshooting: checking the Autodiscover DNS, ensuring port 443 is open, confirming that TLS 1.2 is enabled, and more. However, despite all the checks, Outlook still fails to connect. Given that OWA and ECP are not usable, what steps can I take to restore Outlook 2010 connectivity? I'd appreciate any advice on overlooked configurations or extra diagnostic steps that could help!
2 Answers
It sounds like you're hitting some serious compatibility issues. Outlook 2010 is quite outdated and might not fully support the newer TLS protocols you're trying to use. I'd recommend checking if the new SSL certificate is actually compatible with the backend site. Make sure the trusted certificate is installed on the default web site in IIS as well. Also, you might need to consider upgrading your software if it's a production environment.
Just a heads up, you're working with some seriously old tech here. Have you double-checked that the root CA certificate is still valid? With such outdated systems, that's often a potential roadblock. Also, have you restarted the Exchange server? Sometimes that's all it takes. Good luck!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures