Whats the FQDN of the receive connector and does it match the subject of the GoDaddy Cert?
A community member has associated this post with a similar question:
Exchange Hybrid connector validation from o365 to on-prem
Only moderators can edit this content.
Exchange hybrid connector validation error
Hi,
We recently setup Exchange Hybrid on Classic mode. Completed without errors.
During setup we ensure that the Transport Certificate is valid and we assigned our 3rd party cert (godaddy).
We checked on IIS that "Default Front End" certificates are assigned with 3rd party cert.
IIS 'Exchange Back End' is using the private "Exchange Server" certificate.
When checking Exchange online connectors and validating the O365-Onprem connector, it errors with
"450 4.4.317 Cannot connect to remote server [Message=SubjectMismatch Expected Subject: ...... Thumbprint:######"
When troubleshooting and Checking the certificate thumbprint from the error message on the server. Determined that the thumbprint belonged to the private certificate used in the 'Exchange Back End'
Not sure why it's presenting the wrong certificate and not the front-end certificate?
Normal email flow is still working.
Get-ReceiveConnector 'SERVER\Default Frontend #####' | fl tls*
Shows our public cert with godaddy:
TlsDomainCapabilities : {mail.protection.outlook.com:AcceptCloudServicesMail}
5 answers
Sort by: Most helpful
-
-
Andy David - MVP 150.4K Reputation points MVP
2024-11-04T19:39:45.1366667+00:00 Ok, consider creating a custom receive connector then for the 365> On-prem connection and set the FQDN on that to match the endpoint and cert subject name ( which ever SAN you intend to use) and set the TlsDomainCapabilities : {mail.protection.outlook.com:AcceptCloudServicesMail}
-
Xintao Qiao-MSFT 4,775 Reputation points Microsoft Vendor
2024-11-13T03:18:44.95+00:00 Hi, @Damian M
Here's a similar thread for your reference.
Exchange Hybrid connector validation from o365 to on-prem - Microsoft Q&A
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
-
Damian M 20 Reputation points
2024-11-18T15:16:09.6666667+00:00 Thank you for everyone's input.
Was not able to figure the reason, ended up using the Classic Configuration and it seem to complete without any errors.
-
Xintao Qiao-MSFT 4,775 Reputation points Microsoft Vendor
2024-11-19T07:00:09.37+00:00 Issue Symptom:
After successfully setting up an Exchange Hybrid environment, I encountered an issue where the certificate provided by the 'Exchange Back End' did not match the certificate of the 'Default Front End'.
Resolution:
Using the classic configuration temporarily resolves the problem.