Outlook 2010 Client having autodiscover issues

Hi Guys,

I am having an issues where one outlook 2010 client on our network is having a problem with their autodiscover.

It all started then they were getting a certificate error to say that the name on the site didnt match that on the certifiate. at the top of the certificate the url was autodiscover.domain.co.uk

Now our autodiscover IIS directory is set to its default, so it listens on the autodiscover.domain.local url and we have a SAN SSL certificate with both the external and internal autodiscover domain in it, along with a few others.

I have checked this is still being used in exchange for IIS, and that it is still in the certificate stre with its private key. All other clients work fine except this one, which seems to want to talk to the exchange server using the autodiscover.domain.co.uk domain rather than the autodiscover.domain.local domain it should, therefore a mismatch error.

Also note the client when creating a new outlook profile, cannot autodiscover their account either. I have repaired office 2010 on the client but no results from that.

Any ideas?
LVL 3
sparky2156Asked:
Who is Participating?
 
sparky2156Connect With a Mentor Author Commented:
Issue resolved.

Problem was with a single client not being able to resolve the autodiscover domain, even after re-installing outlook. It wante dto use the external autodiscover URL and neglected the provided internal one.

The external atodiscover url was actually part of the ssl certificate already (as well as the internal one) so I created the external autodiscover subdomain and this resolved the issue.

Thanks.
0
 
MegaNuk3Commented:
What version of exchange is this?

Is the machine with the problem domain joined? Check it's DNS settings and make sure that when you ping the autodiscover names on your certificate that they resolve to the internal IP address of your CAS server
0
 
sparky2156Author Commented:
Exchange 2010. client is just standard DHCP client.

As for the domain, thats a good one. we havnt setup the autodiscover.domain.local in the DNS internally. And the external domain autodiscover.domain.co.uk doesnt even exist, as it isnt actually needed . . .

But if it were a DNS issue, surely it would be systemwide for all users, not just one?
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
MegaNuk3Commented:
Are you using SRV records in DNS?
0
 
AmitIT ArchitectCommented:
Check this too

http://www.theemailadmin.com/2010/02/outlook-and-autodiscover-errors/

It refers to some registry issue at client end
0
 
sparky2156Author Commented:
I am using SRV records in out own DNS for our autodiscover.domain.local domain.

Thanks for the links - i read through them but they still dont explain why the clients are talking to the external DNS recod autodiscover.domain.co.uk

I checked the certificate message again and noticed that the client machine being affected by this is being issued the default self-signed certificate from exchange, and not the one we purchased. I checked the EMC and the purchased certificate is assigned the IIS, SMTP, POP and IMAP services. The only other certificate assigned to anything the the self signed Microsoft Exchange certificate and it has been assigned SMTP, which i cannot remove, although my officially signed certificate is assigned the SMTP role as well.

Why would a client machine be getting the wrong certificate when it is set correclty in exchange?
0
 
AmitIT ArchitectCommented:
0
 
MegaNuk3Commented:
Have a look in IE at the certificates on your problem machine and see if the self signed one exists there or not, if it does then delete it and clear the SSL cache. Also ensure IE is set to bypass proxy for local addresses.

Also ping the autodiscover names from that PC and confirm it is getting the same IP address reply as a working PC, there may be an invalid HOSTS entry on the PC.
0
 
sparky2156Author Commented:
Resolved Issue myself
0
All Courses

From novice to tech pro — start learning today.