asked on Migrating from Exchange 2003 to Exchange Online
We are trying to migrate from Microsoft Exchange 2003 to Microsoft Exchange online. When going through cut-over migration plan, we get this error -
"We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues."
When we are connect, we specify the exchange server and rpc proxy server. exchange server is set to our internal server name. RPC server is set to the mail.server.com. When we run the internal analyzer, we get all clear.
Any ideas on what the issue is? We verified the rpc authentication is set to basic, but are still having issues.
Help! Thanks all!
"We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues."
When we are connect, we specify the exchange server and rpc proxy server. exchange server is set to our internal server name. RPC server is set to the mail.server.com. When we run the internal analyzer, we get all clear.
Any ideas on what the issue is? We verified the rpc authentication is set to basic, but are still having issues.
Help! Thanks all!
Windows Server 2003Microsoft 365
Last Comment
Alan Hardisty
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Yes, there is a 3rd party SSL cert in place. Outlook functions correctly externally.
Have you run the RPC over HTTPS test on testexchangeconnectivity.c
ASKER
We're getting a 'certificate chain did not end in a trusted root' error using the connectivity test.
So that sounds like maybe the certificate that you are presenting is not the correct certificate. Basically what it's telling you is that your PKI chain trust is broken.
I would take a look at the certificate itself and the certificate chain and verify it has a valid trust from the bottom all the way to the top.
I would take a look at the certificate itself and the certificate chain and verify it has a valid trust from the bottom all the way to the top.
Where did you get the very from and did you install the Intermediate Certificate from that provider?
Alan
Alan
ASKER
I just found out it is not a 3rd party cert. Is it possible to migrate without?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Yes like Alan said it has to be trusted. Office365 will not trust your server. You can use other services like MigrationWiz.
https://www.bittitan.com/products/
But a certificate is cheaper.
https://www.bittitan.com/products/
But a certificate is cheaper.
ASKER
Alright, SSL fixed, now getting:
RPC Proxy can't be pinged.
Additional Details
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (401) Unauthorized.
RPC Proxy can't be pinged.
Additional Details
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (401) Unauthorized.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.