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

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
       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=""
X-Powered-By: ASP.NET
Elapsed Time: 619 ms.
      Test Steps
      Attempting to resolve the host name in DNS.
       The host name resolved successfully.
      Additional Details
      Testing TCP port 443 on host 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
       The HTTP authentication methods are correct.
      Additional Details
      Attempting to ping RPC proxy
       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
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Michael B. SmithManaging ConsultantCommented:
I took my blog posts about Exchange 2003 offline years ago. And RPC/HTTP wasn't released when I wrote my book (against TAP and RTM).

But the first thing I would do would be to try rpcping internally and see what it tells you (

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
qAuthor Commented:
Thanks Michael for your response.

i did the tests as recommended in the link above, which let me to a few other checks  netdiag /winsoc /v says It's not the NIC, and i assume winsock is not corrupted - seems like Exchange would be failing if it were.   It's not the certificate (connectivity test passes for the cert).   The error i get from the rcpping is below.  I was not sure of the syntax of the RpcProxyServer part of the command, so i used both the syntax as written and also with the name of my server.  Both failed, but with different results.   I did the test on both the exchange server and another server.  There is not a  lot of informative info about what to do about either error.  Do you have any further input??

I am wondering if i could just try  to continue with the migration anyway and see what will happen, if I get other  errors, maybe they will point me to a fix.

Results of the rpcping - done on the exchange server, and on a different member server gave 12007  and 12175 ping failure error.

C:\Program Files\Support Tools>rpcping -t ncacn_http -s -o RpcProxy=RPCProxyServer -P "*" -I "
*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none
RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
OS Version is: 5.2, Service Pack 2
Enter password for server:
Enter password for RPC/HTTP proxy:

RPCPinging proxy server RPCProxyServer with Echo Request Packet
Sending ping to server
Error 12007 returned in the WinHttpSendRequest.
Ping failed.

C:\Program Files\Support Tools>rpcping -t ncacn_http -s -o "*" -I "
,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none
RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
OS Version is: 5.2, Service Pack 2
Enter password for server:
Enter password for RPC/HTTP proxy:

RPCPinging proxy server with Echo Request Packet
Sending ping to server
Error 12175 returned in the WinHttpSendRequest.
Ping failed.
qAuthor Commented:
Michael, i just found this here, will investigate if i can.



One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server. To determine what type of error was encountered, check for a WINHTTP_CALLBACK_STATUS_SECURE_FAILURE notification in a status callback function. For more information, see WINHTTP_STATUS_CALLBACK.
Price Your IT Services for Profit

Managed service contracts are great - when they're making you money. Yes, you’re getting paid monthly, but is it actually profitable? Learn to calculate your hourly overhead burden so you can master your IT services pricing strategy.

qAuthor Commented:

I dug deep into the WINTHTTP material, can't say it helped at all because i don't know what goes on that far in the background.  But on the journey i found lots of other info on RPC.  Finally found a registry setting that needed to be added on the Exchange server that was not there already. Once I added the key  all is well.

The registry setting for Windows Server 2003 global catalog servers is not
automated by Exchange 2003 setup. This setting must be configured either
manually or programmatically for RPC over HTTP to work. This is scheduled
to be included in Windows Server 2003 Service Pack 1 (SP1).
Parameter: NSPI interface protocol sequences
Value: ncacn_http:6004

Your initial answer led me down the right path, so thanks a lot!
qAuthor Commented:
Thanks Michael.
Michael B. SmithManaging ConsultantCommented:
Oh wow, that's a blast from the past! Glad it helped!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.