wayne70
asked on
RPC Proxy can't be pinged
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.E xRca.Exten sions.Mapi TransportE xception
Stack trace:
at Microsoft.Exchange.Tools.E xRca.Exten sions.Mapi RpcTestCli ent.PingPr otocolProx y(String endpointIdentifier)
at Microsoft.Exchange.Tools.E xRca.Tests .MapiPingP roxyTest.P erformTest Really()
Exception details:
Message: The remote server returned an error: (401) Unauthorized.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest. GetRespons e()
at RpcPingLib.RpcPing.PingPro xy(String internalServerFqdn, String endpoint)
at Microsoft.Exchange.Tools.E xRca.Exten sions.Mapi RpcTestCli ent.PingPr otocolProx y(String endpointIdentifier)
Elapsed Time: 515 ms.
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.E
Stack trace:
at Microsoft.Exchange.Tools.E
at Microsoft.Exchange.Tools.E
Exception details:
Message: The remote server returned an error: (401) Unauthorized.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.
at RpcPingLib.RpcPing.PingPro
at Microsoft.Exchange.Tools.E
Elapsed Time: 515 ms.
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.
ASKER
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.