Problem with site security certificate in Exchange 2010

We have security certificate from trusted authority but now we are getting below error of certificate.

"The name on security certificate is invalid or does not mach the name of the site"

This error pops up frequently in outlook. Kindly assist for the same.
Cert-Error.jpg
sanjayambreAsked:
Who is Participating?
 
vSolutionsITConnect With a Mentor Commented:
use your external domain name mentioned in the certificate and configure your exchange services as mentioned in below articles then check if you are still facing this issue.

http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/configuring-exchange-server-2007-web-services-urls.html

http://exchange.sembee.info/2007/install/singlenamessl.asp
0
 
KorbusCommented:
Can I assume you have a different internal (e.g. exchserv.lanname.local)and external (e.g. mail.domainname.com) server name for your exchange server?   Is that internal name on the certificate?

If this is your issue (answered yes & no above): here is a workaround - you can create a LOCAL dns entry on network to point the external name to your internal exchange server IP address.  (note this will NOT match what the internet says for the giving domain name- which will specify your WAN IP.)  You can then configure outlook using the external name and it will find the server and match the cert.
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,

For this setup you need à SAN certificate (Subject Alternative Name) which contains your internal domain and your external domain.
0
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

 
Gareth GudgerCommented:
Patrick, after 2015, internal names can no longer be used on SAN certificates.

So you are better off setting your Internal URLs to match your External URLs and then using split brain DNS, where you have a non-authoritative copy of your external DNS namespace on your internal DNS servers.
0
 
sanjayambreAuthor Commented:
Yes. we have different internal (e.g. exchserv.lanname.local)and external (e.g. mail.domainname.com) server name for exchange server. Error pops-up is related with internal server name.
0
 
Gareth GudgerCommented:
Yep, just make your internal URLs match your external URLs in Exchange and use split brain DNS to create those external records to map to internal IPs.
0
 
KorbusCommented:
That's called "split-brain DNS"? LOL, love it!
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.