[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 320
  • Last Modified:

Autodiscover not functioning

Email flow is perfect and all working.  I upgraded my spam filter with a 3rd party and now the anti-spam is not working.  They said it is because autodiscover is not working.

I have been to www.testexchangeconnectivity.com and it did come back with some errors.  
When I run
test-outlookwebservices username@domainname.com | FL
 it fails.

The first failure is the second line id 1013 and it reports that "the remote server returned an error: (500) Internal server error.

I tried going to https://domainname/AutoDiscover/AutoDiscover.xml and it does not work.

I can ping autodiscover.domainmae.com from both internal and external to the correct IP.  


Need some quick help.  Thanks,

Brad
0
bhgewilson
Asked:
bhgewilson
  • 4
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
Autodiscover tries a number of hosts by default, one of which is example.com - it would then move on to autodiscover.example.com .

When you run the test you should see it carry on with the additional URLs, the only time the root of the domain would work would be internally if Exchange was installed on a domain controller. Otherwise the root of the domain externally should be pointing to your public web site.

What were the errors from the Microsoft test site?

Simon.
0
 
avcontrolCommented:
Sound like your updates also blocking DNS server.......
If you ping www.yahoo.com for example from CMD , will it return IP address?
If not , then its defiantly DNS issue and as result failed access.....
0
 
bhgewilsonAuthor Commented:
Simon\AV

yahoo works.

Here is the text from the output of www.testexchangeconnectivity.com.
Seeing that I am getting a 500 Error I think it is something to do with IIS but I can't be certain.





ExRCA is attempting to test Autodiscover for bwilson@****.com.
 Testing Autodiscover failed.
 
Test Steps
 
Attempting each method of contacting the Autodiscover service.
 The Autodiscover service couldn't be contacted successfully by any method.
 
Test Steps
 
Attempting to test potential Autodiscover URL https://****.com/AutoDiscover/AutoDiscover.xml
 Testing of this potential Autodiscover URL failed.
 
Test Steps
 
Attempting to resolve the host name ****.com in DNS.
 The host name resolved successfully.
 
Additional Details
 IP addresses returned: 205.178.152.152


Testing TCP port 443 on host ****.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.





Attempting to test potential Autodiscover URL https://autodiscover.****.com/AutoDiscover/AutoDiscover.xml
 Testing of this potential Autodiscover URL failed.
 
Test Steps
 
Attempting to resolve the host name autodiscover.****.com in DNS.
 The host name resolved successfully.
 
Additional Details
 IP addresses returned: 98.101.72.171


Testing TCP port 443 on host autodiscover.****.com to ensure it's listening and open.
 The port was opened successfully.

Testing the SSL certificate to make sure it's valid.
 The certificate passed all validation requirements.
 
Test Steps
 
ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.****.com on port 443.
 ExRCA successfully obtained the remote SSL certificate.
 
Additional Details
 Remote Certificate Subject: CN=mail.****.com, OU=Domain Control Validated, O=mail.****.com, Issuer: SERIALNUMBER=10688435, CN=Starfield Secure Certification Authority, OU=http://certificates.starfieldtech.com/repository, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.


Validating the certificate name.
 The certificate name was validated successfully.
 
Additional Details
 Host name autodiscover.****.com was found in the Certificate Subject Alternative Name entry.


Certificate trust is being validated.
 The certificate is trusted and all certificates are present in the chain.
 
Test Steps
 
ExRCA is attempting to build certificate chains for certificate CN=mail.****.com, OU=Domain Control Validated, O=mail.****.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 OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.


Analyzing the certificate chains for compatibility problems with versions of Windows.
 Potential compatibility problems were identified with some versions of Windows.
 
Additional Details
 ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.




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 = 11/19/2010 5:34:37 PM, NotAfter = 11/17/2013 8:04:42 PM




Checking the IIS configuration for client certificate authentication.
 Client certificate authentication wasn't detected.
 
Additional Details
 Accept/Require Client Certificates isn't configured.


Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
 Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
 
Test Steps
 
ExRCA is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.****.com/AutoDiscover/AutoDiscover.xml for user bwilson@****.com.
 ExRCA failed to obtain an Autodiscover XML response.
 
Additional Details
 An HTTP 500 response was returned from Unknown.






Attempting to contact the Autodiscover service using the HTTP redirect method.
 The attempt to contact Autodiscover using the HTTP Redirect method failed.
 
Test Steps
 
Attempting to resolve the host name autodiscover.****.com in DNS.
 The host name resolved successfully.
 
Additional Details
 IP addresses returned: 98.101.72.171


Testing TCP port 80 on host autodiscover.****.com to ensure it's listening and open.
 The port was opened successfully.

ExRCA is checking the host autodiscover.****.com for an HTTP redirect to the Autodiscover service.
 ExRCA 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 not have permission to view this directory or page.




Attempting to contact the Autodiscover service using the DNS SRV redirect method.
 ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method.
 
Test Steps
 
Attempting to locate SRV record _autodiscover._tcp.****.com in DNS.
 The Autodiscover SRV record wasn't found in DNS.
  Tell me more about this issue and how to resolve it
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
bhgewilsonAuthor Commented:
Anyone have any ideas?
0
 
Simon Butler (Sembee)ConsultantCommented:
This is the only bit of any interest.

ExRCA is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.****.com/AutoDiscover/AutoDiscover.xml for user bwilson@****.com.
 ExRCA failed to obtain an Autodiscover XML response.
 
Additional Details
 An HTTP 500 response was returned from Unknown.


Unfortuantely it is fairly common.
First thing I would do is reset the virtual directory. If you are on Exchange 2010 SP2 there is a wizard in the Client Access part of EMC which will do that for you.

Simon.
0
 
bhgewilsonAuthor Commented:
Simon, I had to go through and call Microsoft.  They had a hotfix where they installed it and rolled back an update.  All is working now.
0
 
bhgewilsonAuthor Commented:
I had to call Microsoft to resolve.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now