troubleshooting Question

Microsoft remote Connectivity analyzer, Outlook Connectivity test fails: cannot ping RPC proxy server

Avatar of q
qFlag for United States of America asked on
ExchangeOutlookMicrosoft 365
6 Comments1 Solution533 ViewsLast Modified:
I had this question after viewing RPC Proxy can't be pinged.  I am preparing for the staged migration to O365 from Exchange 2003,  the Outlook Connectivity test , manually specifying server settings, using basic authentication, fails with the following, but with different exceptions from the previous question.  Our inside domain name is the same as outside. I am able to successfully use https://  public IP address/owa.  Any help will be appreciated.

Testing RPC over HTTP connectivity to server server.domain.org
       RPC over HTTP connectivity failed.
       
      Additional Details
       
HTTP Response Headers:
Content-Length: 1656
Content-Type: text/html
Date: Wed, 05 Sep 2018 19:10:45 GMT
Server: Microsoft-IIS/6.0
WWW-Authenticate: Basic realm="server.domain.org"
X-Powered-By: ASP.NET
Elapsed Time: 619 ms.
       
      Test Steps
       
      Attempting to resolve the host name server.domain.org in DNS.
       The host name resolved successfully.
       
      Additional Details
      Testing TCP port 443 on host server.domain.org to ensure it's listening and open.
       The port was opened successfully.
       
      Additional Details
      Testing the SSL certificate to make sure it's valid.
       The certificate passed all validation requirements.
       
      Additional Details
       
      Test Steps
      Checking the IIS configuration for client certificate authentication.
       Client certificate authentication wasn't detected.
       
      Additional Details
      Testing HTTP Authentication Methods for URL https://server.domain.org/rpc/rpcproxy.dll?server.domain.org:6002.
       The HTTP authentication methods are correct.
       
      Additional Details
      Attempting to ping RPC proxy server.domain.org.
       RPC Proxy can't be pinged.
       
      Additional Details
       
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: Microsoft.Exchange.Tools.ExRca.Extensions.MapiTransportException
Stack trace:
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
at Microsoft.Exchange.Tools.ExRca.Tests.MapiPingProxyTest.PerformTestReally()
Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at RpcPingLib.RpcPing.PingProxy(String internalServerFqdn, String endpoint)
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
Elapsed Time: 48 ms
.
ASKER CERTIFIED SOLUTION
Michael B. Smith
Managing Consultant

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 6 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 6 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros