Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

Autodiscover returns another company's Certificate

$
0
0

I am having a bit of an unusual issue with Outlook 2013 and Autodiscover.  At present for all Office 2010/2007/2003, Android, Apple and Windows phone autodiscover works perfectly without any issue  If I use the MS tool to test autodiscover and outlook anywhere the connection comes back 100% with no errors. 

When I try to connect a new Outlook 2013 client I enter in the clients name, email and password information and the process starts, after a moment we get presented with a certificate error.  The error says it is the wrong name on the certificate and that the certificate is expired.  If I open the certificate presented, it is for a totally different company (www .otherdomain.com) that is hosted at the same Domain\Web Hosting service.  If I click ignore the certificate the autodiscover continues and works but I don't want that happening everytime we setup Outlook 2013....

For our company we use a web hosting services that has our main web site at www .domain.com and dns resolves domain.com to this site as well.  What I think may be happening is Outlook 2013 sends a first autodiscover request to https ://domain.com/autodiscover.  This resolves to our hosted web servers which returns the first hosted client to respond and their certificate which is https ://othercompany.com.  Accepting the certificate allows the request to proceed but then fails when no Autodiscovery response returns from that address in time.  Then it makes a request to autodiscover.domain.com and it succeeds in getting the configuration information.

I have ruled out an issue with our certificate if I check it from the shell or from OWA the alternate names and domain names are correct.

So...I opened a call with our hosting services to see if there was anything they could do on their side but I wonder if this is a bug with Outlook 2013?  Why would my config work with everything else except this one new product?  Has anyone else seen a similar issue?  Is there a way to suppress the first autodiscover request from the outlook client in the registry to confirm my suspicion?


Viewing all articles
Browse latest Browse all 10580

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>