We recently changed our public IP addresses, and now mobile email apps no longer work while away from the network. I updated our external DNS host to include two new A records for mail and autodiscover, so outgoing and incoming emails are coming through fine within the network.
We use Exchange 2010 and Windows Server 2012; both are behind a SonicWall firewall. I have updated the local DNS records and the firewall accordingly. The X1 (primary) and X2 (backup) interfaces reflect the new IP address info. I also created new public_mail and private_mail address objects.
I used the Microsoft Remote Connectivity Analyzer and found that autodiscover is not working (pasted below). It looks like port 443 is not listening/opening. However, I am not sure why. It is configured to open. Any help is much appreciated. Please let me know if you need more information regarding the problem.
Thanks,
Kevin
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for k Testing Autodiscover
failed.
Additional Details Elapsed Time: 5071 ms. Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method. Additional Details
Elapsed Time: 5071 ms.
Test Steps
Attempting to test potential Autodiscover URL https://westm
.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed.
Additional Details Elapsed Time: 3303 ms.
Test Steps
Attempting to resolve the host name westm .com in DNS. The host name resolved
successfully.
Additional Details
IP addresses returned: 104. Elapsed Time: 38 ms.
by GoDaddy
Testing TCP port 443 on host westminstervillagein.com to ensure it's listening and open. The port
was opened successfully.
Additional Details Elapsed Time: 162 ms.
Testing the SSL certificate to make sure it's valid. The certificate passed all validation
requirements.
Additional Details Elapsed Time: 517 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server
westm .com on p The Microsoft Connectivity Analyzer successfully obtained the
remote SSL certificate.
Additional Details
Validating the certificate name.
The certificate name was validated successfully. Additional Details
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate
CN=west .com. One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=DST Root CA
X3, O=Digital Signatur Elapsed Time: 29 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows. Potential
compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root
Certificate Update functionality Update. Your certificate may not be trusted on Windows if the
"Update Root Certificates" feature isn't enabled.
Elapsed Time: 1 ms.
Testing the certificate date to confirm the certificate is valid. Date validation passed. The
certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 7/12/2019 8:26:20 PM, NotAfter = 10/10/2019 8:26:20 PM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication. Client certificate
authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured. Elapsed Time: 1252 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs. Autodiscover
settings weren't obtained when the Autodiscover POST request was sent.
Additional Details
7/28/2019
Microsoft Remote Connectivity Analyzer
Elapsed Time: 1332 ms. Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL
https://west.com:443/Autodiscover/Autodiscover.xml for user one@westm.com.
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response. Additional
Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
HTTP Response Headers:
Transfer-Encoding: chunked Connection: keep-alive Keep-Alive: timeout=20
Vary: Accept-Encoding,Accept-Encoding
Link: <https://westminstervillagein.com/wp-json/>; rel="https://api.w.org/" WPE-Backend: apache
Cache-Control: no-cache, must-revalidate, max-age=0 Content-Type: text/html; charset=UTF-8
Date: Sun, 28 Jul 2019 22:54:49 GMT
Expires: Wed, 11 Jan 1984 05:00:00 GMT Server: nginx
Elapsed Time: 1331 ms.
Attempting to test potential Autodiscover URL https://autodiscover.west
.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed.
Additional Details Elapsed Time: 1385 ms.
Test Steps
Attempting to resolve the host name autodiscover.westm .com in DNS. The host name
resolved successfully.
Additional Details
IP addresses returned: 216.2 Elapsed Time: 26 ms.
Testing TCP port 443 on host autodiscover.westm .com to ensure it's listening and
open. The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 1358 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: 367 ms.
Test Steps
Attempting to resolve the host name autodiscover.westm n.com in DNS. The host name
resolved successfully.
Additional Details
IP addresses returned: 216.2 Elapsed Time: 12 ms.
Testing TCP port 80 on host autodiscover.westm .com to ensure it's listening and
open. The port was opened successfully.
Additional Details Elapsed Time: 130 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.westm .com
for an HTTP redirect to the Autodiscov The Microsoft Connectivity Analyzer failed to get an HTTP
redirect response for Autodiscover.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body
of the response: You do to view this directory or page.
HTTP Response Headers:
Content-Length: 58 Content-Type: text/html
Date: Sun, 28 Jul 2019 22:54:51 GMT
Server: Microsoft-IIS/8.5 X-Powered-By: ASP.NET Elapsed Time: 223 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV
redirect method. Additional Details
Elapsed Time: 9 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.westm .com in DNS. The
Autodiscover SRV record wasn't found in DNS.
https://testconnectivity.microsoft.com/#&&6bcC5mCLIouoADw0Cig+2vSiG8pTcCTQJcd+stP++aHikM5dxPV+EL3774
yp3duvmVT5ySfoC5a991pnFqE… 2/3
7/28/2019
Microsoft Remote Connectivity Analyzer
https://testconnectivity.microsoft.com/#&&6bcC5mCLIouoADw0Cig+2vSiG8pTcCTQJcd+stP++aHikM5dxPV+EL3774
yp3duvmVT5ySfoC5a991pnFqE… 3/3
Sta
Tell me more about this issue and how to resolve it Additional Details
Elapsed Time: 9 ms.
Checking if there is an autodiscover CNAME record in DNS for your domain 'west
.com' for Office 365. Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in
Office 365, you can ignore this warning.
Tell me more about this issue and how to resolve it Additional Details
There is no Autodiscover CNAME record for your domain 'westmi m'.