Forum Discussion
vineyard_166933
Nimbostratus
Strange this, feels like OA should break every time implementing RPC/MAPI from Exchange iApp.
Since LTM rejects all unspecified ports natively, and Outlook Anywhere sends RPC traffic to the RPC/Mapi VIP on 6001-6004 port range.
OA will proxy traffic to DNS name specified in the Exchange RPCCLIENTACCESSSERVER property. And by recommendations the property points to the RPC/Mapi VIPs DNS name.
vineyard_166933
Dec 05, 2014Nimbostratus
Yes, you are right. OA clients connect on 443 and rpc/mapi on 135 and two static ports.
But after that, 6001-6004 is static default ports used to connect to cas and mailbox servers.
If you want you can search for "rpc over http" on this url and there is a brief explanation:
http://blogs.technet.com/b/exchange/archive/2012/03/23/demystifying-the-cas-array-object-part-1.aspx
In fiddler it will look like this:
https://mail.hostname.com/rpc/rpcproxy.dll?CASARRAY.local:6002 HTTP/1.1
If there was a way to separate what CAS servers OA and rpc/mapi connects to it would be a solution also.
Tested with remote connectivity analyzer also. OA works when specifying an internal exchange server.
IE. when using 6001-6004 against a CAS server directly instead of the F5 VIP.