Troubleshooting RPC Problems

For troubleshooting RPC problems try the following;
 Using RPCping to ensure it is working between both servers.


Ensure you have port 135 and ports 1024-65,535 open for the dynamic RPC range. You can do this by using the Port Query tool (PortQry and PortQueryUI). Example: portqry -n [servername] -e 135 AND portqry -n [servername] -e 1024-5000 .


If you do not want to use that large of range you must define the ports and change the following registry key. When picking RPC ports you should select a range over 60,000 to avoid NSPI proxy warning errors. I use 60,000 - 65,535.


HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters


Data type = REG_DWORD


Port range = 5000 – 65534


Default = 5000






You can try setting your TCP packet acknowledments to 3 instead of 5. KB 170359


HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters


Data type = REG_DWORD


Valid range = 0 - 0xFFFFFFFF (hexadecimal)


Default = 5






Look through your Event Logs for a more specific RPC error. For a complete list of RPC error codes go to http://msdn2.microsoft.com/en-us/ms681386.aspx . Some of the most common ones are:


58 = The specified server cannot perform the requested operation.


1721 = Not enough resources are available to complete this operation.


1722 = The RPC server is unavailable.


1723 = The RPC server is too busy to complete this operation.


1727 = The remote procedure call failed and did not execute.


1753 = There are no more endpoints available from the endpoint mapper.


Try running repadmin /bind, if you are having RPC problems it might respond back with an endpoint mapper error.