Cannot set out of office. Auto-discover test fails. Outlook / Exchange 2010

Hello,

Any help greatly received.

There appears to be alot of information available out there, although no clear and concise explanation of the problem at hand.

Existing and new users are unable to set the out of office within Outlook 2010 in an Exchange 2010 environment. (SBS2011)

The autodiscover internal and external url settings are https://mail.domain.com/autodiscover/autodiscover.xml with a valid SSL certificate installed.

An A record exists within DNS so that mail.domain.com resolves internally to the Exchange server.  The EWS address is also https://mail.domain.com/EWS/Exchange.asmx

Running a test autoconfiguration results with the following:  

attempting url  https://mail.domain.com/autodiscover/autodiscover.xml found through scp
autodiscover to https://mail.domain.com/autodiscover/autodiscover.xml starting
autodiscover to https://mail.domain.com/autodiscover/autodiscover.xml failed (ox800c8203)
etc etc

Local autodiscover for domain.com starting
Local autodiscover for domain.com failed (ox8004010f)

Thank you
utilizeAsked:
Who is Participating?
 
utilizeAuthor Commented:
this ended up being a problem with a stale DNS entry on a PC which wouldn't clear. A rebuild of the OS fixed the issue.
0
 
Simon Butler (Sembee)ConsultantCommented:
As this is SBS, did you setup the server using the wizards?
Do you have a trusted SSL certificate on the server? If so, does the name match what you have configured Exchange to use?
The error code you have posted is usually a DNS error, so I would check name resolution is correct.  You shouldn't have any external DNS servers in the network configuration of the workstations or server - if you need to use an external DNS server then it should be set as a forwarder in the DNS server applet.

Simon.
0
 
utilizeAuthor Commented:
Hello Simon,

Indeed, wizards were used. The SSL certificate does match the configured name for Exchange and the URLs.

No external DNS servers are used.

Thank you,
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Simon Butler (Sembee)ConsultantCommented:
Is the certificate trusted?
If you browse to the URL mentioned for Autdiscover do you get a certificate prompt? You should just get an authentication prompt (Which will never work without error, which is to be expected).

Does the SBS server host any other web sites, except for the defaults of course.

Simon
0
 
utilizeAuthor Commented:
the certificate is trusted, it's from a trusted external CA.

no certificate prompt, just the authentication.

SBS doesn't host any sites other than the defaults
0
 
Simon Butler (Sembee)ConsultantCommented:
Lets go back to basics - in IIS Manager, look at the SSL certificate configuration and ensure that Client Certificates is set to IGNORE, not ACCEPT.
After changing it, run IISRESET and test again.

Simon.
0
 
utilizeAuthor Commented:
Thanks Simon. Client Certificates are already set to Ignore on SSL.

Here are the settings:

Autodiscover:
Require SSL - NO
Client Cert - Ignore

EWS:
Require SSL - NO
Client Cert - Ignore

OAB:
Require SSL - NO
Client Cert - Ignore

RPC:
Require SSL - YES
Client Cert - Ignore
0
 
utilizeAuthor Commented:
0
 
Simon Butler (Sembee)ConsultantCommented:
In that case it is either a DNS configuration error or something is wrong with the SSL certificate. The error code you are getting is a cannot connect, and is usually one of those two items.

You need to check the DNS again, ensure that the client resolves it correctly.
Then you will need to speak to your SSL provider and ask about rekeying the certificate. They shoudl do that free of charge.

Simon.
0
 
utilizeAuthor Commented:
thank you - i will try the rekey. I'm pretty confident that DNS is okay.
0
 
utilizeAuthor Commented:
okay - the certificate has been reissued but the problem persists.
0
 
Simon Butler (Sembee)ConsultantCommented:
I haven't really got anything else to suggest.
This fails for a small number of reasons, and while you are confident you have DNS correct, I have to suspect that either that is the problem, or the host names aren't configured correctly.

You can try re-running the wizards in SBS again, which should correct things. Ensure that the clients are using ONLY the SBS Server for DNS, no external servers.

Simon.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.