Certificate common name mismatch error

[MillMaster]

I have my "default website" running OWA for exchange users. I installed a certificate but I still get a certificate error that says "the name on the security certificate is invalid or does not match the name of the site."

Where exactly is it that the comparison is made between the CN on the certificate and the website?

At the top level properties for the "default website" under website ID, I have 2 identities for port 80 (the local and the public IP address, with host header values both set to the CN)
and I have one SSL entry. (only referencing the local IP) Do I need a second SSL entry listing the public IP?


Also, does anyone know why when I install an intermediate .p7b certificate in the MMC it acts like it installs correctly, but then never shows the certificate under the intermediate cert. folder?

Thanx in advance for any help... (...why cant users just deal with ip addresses and certificate errors ...)

 

[reynolwi]

i have never had any problems with my godaddy certs and i just setup a new server for sharepoint and have an ssl cert for it as well and didnt have problems with the intermediate certs from godaddy.

the common name is suppose to be what it is going to be called on the outside world or intranet. Mine i just setup is portal.domain.net and i just ensured that all my DNS servers had an A record for "portal" and my DNS records outside had an A record for "portal".

I do not think you can redirect to an IP address with an SSL cert. I do believe it has to be a common name permenantly.

Wm. Reynolds
RRWDS | TxPSS

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -
Network Error:
Hit any user to continue