asked on Muthual Authentication
My two Exchange Servers suddenly stopped to configure Outlook clients via autodiscovery. Srv06 is running Exchange Server 2010 and Srv07 is running Exchange Server 2012. The both are virtual servers running under a Windows Server 2008 with Hyper-V.
The testexchangeconnectivity website reports the following errors:
Srv06 (Exchange 2010):
Testing SSL mutual authentication with the RPC proxy server.
Verification of mutual authentication failed.
The certificate common name *.larsoft.net doesn't validate against the mutual authentication string that was provided: msstd:srv06.larsoft.net
Srv07 (Exchange 2013):
Testing SSL mutual authentication with the RPC proxy server.
Verification of mutual authentication failed.
The certificate common name *.larsoft.net doesn't validate against the mutual authentication string that was provided: msstd:srv07.larsoft.net
The certificate seems to be ok. It's a wildcard certificate (*.larsoft.net) for both servers, it's issued by Comodo and the expiration date is May, 30, 2013.
Opening the certificate in Exchange Management Console, the certificate status is "This certificate is OK."
Do you have any idea of what is happening with my Exchange Servers?
Thanks in advance,
Luciano Reis
The testexchangeconnectivity website reports the following errors:
Srv06 (Exchange 2010):
Testing SSL mutual authentication with the RPC proxy server.
Verification of mutual authentication failed.
The certificate common name *.larsoft.net doesn't validate against the mutual authentication string that was provided: msstd:srv06.larsoft.net
Srv07 (Exchange 2013):
Testing SSL mutual authentication with the RPC proxy server.
Verification of mutual authentication failed.
The certificate common name *.larsoft.net doesn't validate against the mutual authentication string that was provided: msstd:srv07.larsoft.net
The certificate seems to be ok. It's a wildcard certificate (*.larsoft.net) for both servers, it's issued by Comodo and the expiration date is May, 30, 2013.
Opening the certificate in Exchange Management Console, the certificate status is "This certificate is OK."
Do you have any idea of what is happening with my Exchange Servers?
Thanks in advance,
Luciano Reis
Microsoft Server AppsServer SoftwareOutlook
Last Comment
informago
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a questionAll of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Thumbprint Services Subject
<thumb> IP..S. CN=Srv06
<thumb> ...... CN=WMSvc-Srv06
<thumb> ...W.. CN=*.larsoft.net, OU=comodo SSL Wildcard, OU=Dom...
The same command on Srv07 result the following:
Thumbprint Services Subject
<thumb> ....S.. CN=Microsoft Exchange...
<thumb> IP.WS.. CN=Srv07
<thumb> ....... CN=WMSvc-Srv07
<thumb> ...WS.. CN=*.larsoft.net, OU=Comodo...