Failed to ping Endpoint 6004 - An RC Error was thrown by the RPC Runtime process...
I recently started having issues with RPC over HTTP. I have been successfully functioning with RPC over HTTP for years now. Environment: Main Server: Windows 2003 running Terminal Server Exchange Server: Windows 2003 with Exchange 2003 - I have the RPCProxy set for accessing the internal Exchange Server. Nothing has changed concerning the registry or anything (no updates and etc.). I ran the test on www.testexchangeconnectivity.com and received the following error: Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server. An error occurred while testing the NSPI RPC endpoint. Test Steps Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server exserver.newmanchiropractic.com. The attempt to ping the endpoint failed. Tell me more about this issue and how to resolve it Additional Details The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process. When on the internal server, I can telnet to port 6001 & 6002, but receive nothing when trying to telnet to port 6004. I'm not sure how to troublshoot this issue or resolve it. Hoping someone can lead me in the correct direction and on where to start. I will try to reply with as much detail as possible. Thanks, Jake
December 20th, 2010 1:43am

Hi, Please use the RPCping to test the OA: 1. Download the and install RPCping on your external client. http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en 2. Run the following command to verify if the the client is able to connect to proxy server without problem: rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v 3 -E -R none Note: Replace YourExchMBXServer with the FQDN of your exchange server , replace YourRPCProxyServer with the FQDN of your IIS proxy server. -H, This argument is the authentication type that is used for the RPC Proxy server. Use the value 1 for basic authentication, and use the value 2 for NTLM authentication. - F, These arguments are the flags that pass for RPC/HTTP front end authentication. The No SSL flag is 2, and the Use SSL flag is 3. the RPC Ping Utility test was successful, you will receive the following reply: RPCPinging proxy server ExchServer with Echo Request Packet Sending ping to server Response from server received: 200 Pinging successfully completed in Response_Time ms Then move to next step to test if the external client can connect to the validports on the mailbox server: 3. Type: rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v 3 -e:6001 rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v 3 -e:6002 rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v 3 -e:6004 If the RPC Ping Utility test was successful, you will receive the following reply: Completed 1 calls in xxx ms If you receive any errors, please post it here for further research. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT
Free Windows Admin Tool Kit Click here and download it now
December 21st, 2010 8:55pm

Hello Gen, We have the same problem as Jacob mentioned before: a Failure when we try to ping Endpoint 6004. When testing with rpcping: rpcping -t ncacn_http -s srv***.***.*** -o RpcProxy=webmail.***.nl -P "*,*,*" -I "*,*,*" -H 1 -u 10 -a connect -F 3 -v 3 -E -R none RPCPinging proxy server webmail.***.nl with Echo Request Packet Sending ping to server Response from server received: 200 Pinging successfully completed in 1981 m But: rpcping -t ncacn_http -s srv***.***.*** -o RpcProxy=webmail.***.nl -P "*,*,*" -I "*,*,*" -H 1 -u 10 -a connect -F 3 -v 3 -e 6004 Exception 1722 (0x000006BA) Number of records is: 2 ProcessID is 5160 System Time is: 1/19/2011 10:1 Generating component is 14 Status is -1073606647 Detection location is 1398 Flags is 0 NumberOfParameters is 2 Long val: 4 Long val: -1073606647 ProcessID is 5160 System Time is: 1/19/2011 10:1 Generating component is 13 Status is -1073606647 Detection location is 1401 Flags is 0 NumberOfParameters is 0 port 6004 not OK, ports 6001 and 6002 working fine. We are running Exchange 2003 sp2 on W2K3 sp2 in an front-end, back-end scenario. Recently my colleges installed two new DC's on W2K8 R2 OS, can that be a problem?
January 19th, 2011 10:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics