• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 408
  • Last Modified:

Exchange 2010 AutoDiscover

I am having an issue with Autodiscover in Exchange 2010.  I've gone through all of the settings and they all seem to be ok.  I've recreated the Autodiscover virtual directory in IIS7 and it still isn't working.  When I do a test email autoconfiguration from inside the domain I get the attached message.  Anyone know what needs to be done?  I have updated our external DNS with a record for autodiscover.  When I go to testexchangeconnectivity.com I get the second attachment. AutodiscoverErrorInside..docx
0
MHCIT
Asked:
MHCIT
3 Solutions
 
setasoujiroCommented:
Did you create the "autodiscover.domain.com" record on both your external DNS as your domain DNS?
if not, try that and do the test again.

also you can use : testexchangeconnectivity.com
to see if all is well on the outside
0
 
Shreedhar EtteCommented:
- To resolve this issue you need to set the Client Certificates setting to "Ignore" under the Autodiscover virtual directory in IIS manager.


autodiscover.jpg
0
 
MHCITAuthor Commented:
I put in the _autodiscover entry into our external DNS (FRII.com) and our internal but I'm not sure if they are set up correctly.  Is there something somewhere that I can compare it to?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
setasoujiroCommented:
_autodiscover what do you mean by this? i assume an srv record...?
but you should have an A record both in and external pointing to your server :

click admin. tools-->dns-->click your "PBLIC" zone (not the .local) and check if there s an A record for autodiscover.yourdomain.com
if not make one pointing to your local IP

and the external dns should have one, poiting to your EXTERNAL IP

refer to this:

http://technet.microsoft.com/en-us/library/bb201695.aspx
0
 
Suliman Abu KharroubIT Consultant Commented:
when testing your IP address as attached. port 443 is blocked.

Please make sure that you have forward/publish that port in you firewall to exchange server.
0
 
MHCITAuthor Commented:
This was being caused by our external DNS provider.  They didn't know how to set up a SRV record in their system.  We are currently looking for a new external DNS provider.
0
 
MHCITAuthor Commented:
It was a mixture of fixes that finally fixed it.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

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