Problem configuring and testing static ports on CAS servers

Problem Description: You configure the RCA (RPCClientAccessServer) service and AB (Address Book) service to use static ports according to your hardware loadbalancer documentation or technet article.  After a restart of these services you verify the server is listenting on the correct ports.  When testing from an Outlook client, you notice that the Outlook client is using port 7380 for its mail (RCA) connection and the correct static port for directory (AB.)

Error:  There is no error per se, but a netstat -na from a remote Outlook client (typically on a routed network) will appear to persistently bind on on port 7380, even after restart of client. Often times, local clients adjacent to the CAS will bind on the correct static port that you previously set in the registry.

Description:  Port 7380 is a dead giveaway that there is a riverbed in the mix.  Riverbed devices instruct
Outlook to connect over port 7380, regardless of the static port configured for RCA on the CAS.

Solution or Workaround:  No solution is neccessary. Rest assured that the riverbed will use the proper static port configured on the CAS and loadbalancing should work fine.  You can verify this functionality by reviewing your riverbed log.

Registry settings for Exchange 2010 SP1 RCA and AB static ports below:

HKEY_LOCL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRpc\ParametersSystem
REG_DWORD:TCP/IP Port
value:59531-60554

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters
REG_SZ:RpcTcpPort
Value:59531-60554

See Also:

http://social.technet.microsoft.com/wiki/contents/articles/configuring-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx

http://technet.microsoft.com/en-us/library/ff625248.aspx

Grade:  Who Knew?