We help IT Professionals succeed at work.

RPC Proxy can't be pinged

wayne70 asked
Last Modified: 2017-04-19
Outlook anywhere in Exchange 2016 seems to be working via https but if I close outlook and re-open it it says the server is not available.  If I remove the Exchange account from outlook and configure it new everything works until I restart outlook and the problem starts all over again.
Here is the output of the outlook connectivity tester:

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.
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: (401) Unauthorized.
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: 515 ms.
Watch Question

Adam BrownCloud Security Consultant
Top Expert 2010

Run get-outlookanywhere | fl on the Exchange server and verify the internal and external URLs are valid (they should also be the same). Once that's done, open your DNS configuration and make sure there aren't multiple IP addresses assigned to the host name in the OutlookAnywhere URLs. You may be running into a DNS round robin issue.


The command shows the external and internal hostnames are valid but they are different.  The internal name resolves to the private IP of the server and the external name resolves to the Public IP of the server.  How do I go about making them the same and should they point to the private or the public address for outlookanywhere to work?
Cloud Security Consultant
Top Expert 2010
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)


Adam thank you so much for your help with this issue.  I corrected the problem with the Connectivity Tester.  The tester passes with minor issues (certificate may not work on windows phone) not a problem in this environment.  Outlook clients are now connecting and working fine.  When outlook is closed and re-opened it's able to reconnect without a problem.  (internally and externally) On some outlook clients from the external I had to remove the exchange account and re-add it.  After that everything worked fine. Here are the steps I took:

I made it so the urls for the internal and the external match (example: mail.contoso.com)  under server > server > name of server to change > outlook Anywhere
I then created a new DNS zone (contoso.com) and added the an "A" record for the newly added url.  Now the internal clients resolve the url mail.contoso.com to the private address of the exchange server and the external clients resolve the url mail.contoso.com to the public IP of the server.

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions