Microsoft Remote Connectivity Analyser

We have an Exchange Server we want to move to Office 365. There is a front-end and back-end server. When I run the Microsoft Remote Connectivity Analyser (Connectivity Test) we get the following message:

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: 556 ms.

Any suggestions to what this relates to:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Randy DownsOWNERCommented:
Maybe this will help. They were having issues with Exchange 2007 mailboxes but it worked Ok on 2013. Eventually he gave up on fixing this "error"

I can telnet the Exchange server on port 6004. In fact, I can telnet all Exchange servers on that port.

I should add that we are in the process of migrating users from a 2007 to a 2013 server. The test I originally posted was for 2007 mailbox. If I test Outlook connectivity for a 2013 server mailbox then it works fine, so it looks like a 2007 issue.

The Exchange 2007 server in question only has one IPV4 address on the LAN adaptor.

No resolution, although I don't think it's causing any problems. I just don't like the official Microsoft tool telling me there's a problem

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
mail2clkAuthor Commented:
I did some configuration and I am now receiving the error. Does anyone have any suggestions to overcome this issue?

Testing the address book "Check Name" operation for user against server our-exchange.
       An error occurred while attempting to resolve the name.
      Additional Details
An RPC error was thrown by the RPC Runtime process. Error 1717 UnknownIf
Elapsed Time: 1577 ms.
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
Windows Server 2003

From novice to tech pro — start learning today.