How to Verify That the Client Can Contact Backend Ports

Wednesday, November 5, 2008

By default, the RPC Proxy server does not publish the EPM port location. Therefore, you cannot ping the EPM from outside your intranet or use the UUID of the service.

However, you can specify the backend port that you want to test. By default, the store is on port 6001 and DsProxy is on port 6004. If these locations have been changed, the ports can be verified by using the RpcDump utility. The RpcDump utility is available from the Microsoft Windows Server 2003 Resource Kit package. Additionally, Microsoft does not recommend publishing the global catalog Directory Service or the Exchange referral service.

The following RPC Ping Utility examples are typed in at the command prompt. To access the command prompt, click Start, point to All Programs, point to Accessories, and then click Command Prompt.
How to Use Basic Authentication and SSL to Connect to the Store’s Port
Syntax:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001
How to Use Basic Authentication, SSL, and Mutual Authentication to Connect to the Store’s Port
Syntax:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001 –B msstd:server_certificate_subject
How to use NTLM Authentication and Non-SSL to Connect to DsProxy Service
Syntax :
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 2 –F 2 –a connect –u 10 –v 3 –e 6004

0 Comments: