Solved

Muthual Authentication

Posted on 2013-01-04
2
1,057 Views
Last Modified: 2013-01-07
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
0
Comment
Question by:informago
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
2 Comments
 

Author Comment

by:informago
ID: 38746197
The result of Get-ExchangeCertificate on Srv06 result the following:

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...
0
 

Accepted Solution

by:
informago earned 0 total points
ID: 38750821
I found the answer here:

http://www.cgoosen.com/2010/11/outlook-anywhere-and-wildcard-certificates/

It's was basically:

Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.larsoft.net
0

Featured Post

Enroll in June's Course of the Month

June’s Course of the Month is now available! Experts Exchange’s Premium Members, Team Accounts, and Qualified Experts have access to a complimentary course each month as part of their membership—an extra way to sharpen your skills and increase training.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this step by step procedure, you will come to know the details of creating an Outlook meeting in 2007, 2010, 2013 & 2016.
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question