Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Exchange 2013 - outlook 2013 connects through windows 10 but not on windows 7 computers

$
0
0

New exchange 2013 install with coexistent with exchange 2007 to move mail boxes. All data moved over. installed go daddy ucc certificate. Everything working. After updates and a reboot of the server outlook 2013 or outlook 2010 on win 7 machines will not connect to the exchange 2013. Same account set up on a win 10 with outlook 2013 or 2016 connects. SSl now fails connectivity test.  

Had to adsi edit remove the public folders from the exchange 2007 box. We didn't use them. don't think this could affect it but thought I would throw it in.

I ran check with digicert and the ssl chain is good. All phones and remote outlook 2013 on win 10 work remotely.

I have been over all urls on the virtual directory's and autodiscover. They are correct

Nothing in the event viewer.

The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.

I cannot find anything causing this

Any ideas greatly appreciated.

Why would outlook 2013 or 2016 on win 10 connect and on win 7 machines not?

How can the connectivity analyzer fail with below and our remotes all work?  

thanks in advance

Attempting to test potential Autodiscover URL https://autodiscover.-------.com:443/Autodiscover/Autodiscover.xml
 Testing of this potential Autodiscover URL failed.
 
Additional Details
 
Elapsed Time: 1023 ms.
 
Test Steps
 
Attempting to resolve the host name autodiscover.---------.com in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 68.67.245.24
Elapsed Time: 352 ms.
Testing TCP port 443 on host autodiscover.----------.com to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 338 ms.
Testing the SSL certificate to make sure it's valid.
 The SSL certificate failed one or more certificate validation checks.
 
Additional Details
 
Elapsed Time: 332 ms.
 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.---------.com on port 443.
 The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
 
Additional Details
 
The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
Elapsed Time: 301 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
 The attempt to contact Autodiscover using the HTTP Redirect method failed.
 
Additional Details
 
Elapsed Time: 962 ms.
 
Test Steps
 
Attempting to resolve the host name autodiscover.---------.com in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 68.67.245.24
Elapsed Time: 4 ms.
Testing TCP port 80 on host autodiscover.---------.com to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 334 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.----------.com for an HTTP redirect to the Autodiscover service.
 The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
 
Additional Details
 
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Wed, 18 Jan 2017 21:15:39 GMT
Server: Microsoft-HTTPAPI/2.0
Elapsed Time: 623 ms.


Wade





Viewing all articles
Browse latest Browse all 7129

Trending Articles



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