There is a problem with the proxy server's security certicate. The name on the security certificate is invalid or does not match the name of the target site

We have a Server 2003 terminal server that is using Outlook 2010 to connect to Exchange 2010.  We are using an SSL wildcard certificate.  I recently upgraded Exchange from 2003 to 2010 when I noticed some Outlook users on the terminal server were getting "Server unavailable" when opening Outlook.  It was resolved by reconfiguring the profile.

I recently rebooted the terminal server and now when anyone opens Outlook, it will give the error message:

"There is a problem with the proxy server's security certicate. The name on the security certificate is invalid or does not match the name of the target site

Outlook is unable to connect to the proxy server. (Error Code 0)"

When I attempt to reconfigure the profile, with autodiscover or manually, I am prompted to authenticate.  Even though I am using the correct credentials, it does not log in after several trires.  When I hit cancel, I get the message:

"Outlook cannot log on.  Verify you are connected to the network and are using the proper server and mailbox name.  The connection to Microsoft Exchange is unavaliable.  Outlook must be online or connected to complete this action."

This MS article desribes pretty well what is happening.

I follow the resolution and go to https://serverip/rpc, I see "Mismatched address" where the lock would be in the browser confirming I have a secure connection.  I click on View Certificates and am presented with my wilcard certificate.  I install it into root store as directed.

Unfortunately, this does not resolve my problem.  Can anyone suggest where I can go from here to resolve this?

I found another article that explains some of the mechanics behind what's going on with this process, but I'm not entirely sure if it is the answer to my specific problem.
Who is Participating?
LCGS-CorpConnect With a Mentor Author Commented:
This problem had nothing to do with Exchange.  It was about time.  After I rebooted the server I noticed an error in the logs stating that the time between the client and server was skewed.  I have the PDC using navy time for NTP.  All the clients on the network sync time with the PDC.  I double checked and all clients had the same time as the PDC.  Then I checked the time on my VMware ESXi 4 server where the Exchange VM is.   It was not configured for NTP and was about 10 minutes off.  I entered the navy server in the NTP settings for VMware and rebooted Exchange.  No more error.. now all Outlook clients can connect to Exchange.
If the terminal server is internal then outlook should be using TCP/IP and not HTTP to connect to exchange can you confirm? Start outlook with /rpcdiag to check

Another thing to test would be to go into the Outlook HTTP settings and Untick the "only connect to servers with this principal name in their cert" ensure authentication is basic and then test again.
"" is the external name used for owa i assume.
you have a certificate with a subject name "*" ?
is the name of your active directory forest is "" or "domain.other" ?
because if this is the second case, the name of the certificate will always mismatch.
instead using wildcard certificate, you should use a SAN (subject alternate name) in your certificate and include the FQDN of your exchange 2010 server. "server.domain.other"
instead adding the certificate of your web server into the trusted root store, you should import in the trusted root store the public key certificate of the certification authority which delivered the certificate.
unless this is a self signed certificate, in this case the certificate hasn't CA.
Thanks for the solution
LCGS-CorpAuthor Commented:
"Please state your reason for accepting your own comment as the solution?".. I'm not sure what else I can say here other than 'because it was the right answer'
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.