Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 3 subscribers
  • Views 26962 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RPC over HTTP dont work on Reverse Proxy

Vahraba

Hi, 

Since last week, I tried to publish an Exchange 2013 Server on my reverse proxy, but I have all the time the same error. 

All services work perfectly except Outlook Anywhere. So, when I do a testconnectivity I have the following error: 

Attempting to ping the MAPI Mail Store endpoint with identity: a55dca38-ec75-417a-8dc2-7a70a2ce58d1@........com:6001.
  The attempt to ping the endpoint failed.
 
Additional Details
 
An RPC error was thrown by the RPC Runtime process. Error 1818 CallCancelled
Elapsed Time: 37655 ms.

But when I do a DNAT and open port 443, The RPC error disappears.

Can you help me to find a solution please?

P.S: I follow this configuration : http://networkguy.de/?p=998



This thread was automatically locked due to age.
Parents
  • 0
    Here another information, but I don't if it was fixed:

    ID32217 9.203 Outlook anywhere behind the WAF didn't work
    ------------------------------------------------------------------------
    Description: If an Outlook Anywhere is behind the WAF and the test tool
    from microsoft (testconnectivity.microsoft.com/)
    is used you will get some errors in the output from the
    test tool.
    But there is no issue when you use the WAF config for the
    outlook client. Everything works fine and the error from
    the test tool can be ignored.
    Workaround: Independent from the error in the output of the microsoft
    test tool you can use the OA config for outlook on the
    clients.
    Fixed in:
Reply
  • 0
    Here another information, but I don't if it was fixed:

    ID32217 9.203 Outlook anywhere behind the WAF didn't work
    ------------------------------------------------------------------------
    Description: If an Outlook Anywhere is behind the WAF and the test tool
    from microsoft (testconnectivity.microsoft.com/)
    is used you will get some errors in the output from the
    test tool.
    But there is no issue when you use the WAF config for the
    outlook client. Everything works fine and the error from
    the test tool can be ignored.
    Workaround: Independent from the error in the output of the microsoft
    test tool you can use the OA config for outlook on the
    clients.
    Fixed in:
Children
No Data
Unfiltered HTML