Exchange 2010 Autodiscover cerfication error

Hello!
I have a problem with my Exchange 2010 server.
When users connect while on the domain they get the autodiscover uri from AD and that works great.
However, when connected outsite the domain - they get a certification error stating "The name on the security certification is invalid or does not match the name of the site."

I have been googling this for a while now and tryed all kinds of soloutions with no success.
I have;
Point DNS from autodiscover.domain.com TO mail.domain.com
My autodiscover Url is set to https://mail.domain.com/autodiscover/autodiscover.xml

The problem is, the cert is for mail.domain.com and this does not match with autodiscover.domain.com !

This is from testexchangeconnectivity.com

Attempting to test potential Autodiscover URL https://autodiscover.domain.com/AutoDiscover/AutoDiscover.xml
 	Testing of this potential Autodiscover URL failed.
 	
	Test Steps
 	
	Attempting to resolve the host name autodiscover.domain.com in DNS.
 	The host name resolved successfully.
 	
	Additional Details
	Testing TCP port 443 on host autodiscover.domain.com to ensure it's listening and open.
 	The port was opened successfully.
	Testing the SSL certificate to make sure it's valid.
 	The SSL certificate failed one or more certificate validation checks.
 	
	Test Steps
 	
	ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.domain.com on port 443.
 	ExRCA successfully obtained the remote SSL certificate.
 	
	Additional Details
	Validating the certificate name.
 	Certificate name validation failed.
 	 Tell me more about this issue and how to resolve it
 	
	Additional Details

Open in new window


Please, anyone who could assist me?
LVL 3
tigerffsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tigermattCommented:
>> My autodiscover Url is set to https://mail.domain.com/autodiscover/autodiscover.xml

I presume you are referring to the autodiscover URL you have set in your Service Connection Point (SCP) for internal purposes? (Set using Set-ClientAccessServer -AutodiscoverServiceInternalUri)

If so, the SCP is valid only for domain-joined machines. If you are connecting externally or from a non-domain machine, the value stored in Active Directory is not available to those computers. In these cases, Outlook automatically infers the URL, trying https://<smtp-domain>/Autodiscover/Autodiscover.xml and then https://autodiscover.<smtp-domain>/Autodiscover/Autodiscover.xml. <smtp-domain> is the part of the @ in the email address Outlook is supplied with.

In this case, the process will fail because your SSL certificate does not mention autodiscover.domain.com as a valid DNS name.

How to resolve the problem?

Purchase a Unified Communications certificate from somewhere like GoDaddy which lists the autodiscover domain in addition to the mail domain. This is the standard practice.
Remove your autodiscover.domain.com record from external DNS and instead use the SRV connection point method to direct Autodiscover to the mail.domain.com record: http://support.microsoft.com/kb/940881 - this method does require your public DNS provider to support SRV records. Many do not.
Use a wildcard certificate - not something I would recommend. I have had issues with wildcard certificates, and they are generally a lot more costly than a multi-name SAN/UC certificate anyway

-Matt

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
emadallanCommented:
generate a new cert request from exchange 2010 and include all your FQDN, then purshace UCC   cert from a public CA.
continue your pending request in exchange 2010 console.
tigerffsAuthor Commented:
I did the SRV though our DNS supplier and got it working, thank you for your assistance.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.