RPC is used by several components in Windows Server, such as the File Replication Service (FRS), Active Directory Replication, Certificate services, DCOM, domain join, DCPromo and RDP, NLB and Cluster, Microsoft Operations Master, Exchange and SQL. The result is again bundled and passed back to the client, where it is converted to a return value for the client’s procedure call. The arguments are then unpacked and run on the server. During this process, the procedure call arguments are bundled and passed through the network to the server. The client makes a procedure call that appears to be local but is actually run on a remote computer. The RPC protocol is based on a client/server model. Remote Procedure Call (RPC) is an inter-process communication technique to allow client and server software to communicate on a network. I found this very interesting article about how to troubleshoot RPC communications: Netsh int ipv6 set dynamicport udp start=5200 num=10200 Netsh int ipv6 set dynamicport tcp start=5200 num=10200 Netsh int ipv4 set dynamicport udp start=5200 num=10200 Netsh int ipv4 set dynamicport tcp start=5200 num=10200 Reg add HKLM\SOFTWARE\Microsoft\Rpc\Internet /v UseInternetPorts /t REG_SZ /f /d Y Reg add HKLM\SOFTWARE\Microsoft\Rpc\Internet /v PortsInternetAvailable /t REG_SZ /f /d Y Reg add HKLM\SOFTWARE\Microsoft\Rpc\Internet /v Ports /t REG_MULTI_SZ /f /d 5200-10200 ![]() You can customize that port range that RPC will use if you wish, like so: This pool of port numbers is by default 1024-5000 on XP/2003Īnd below, and 49152-65535 on Vista/2008 and above. Which are drawn from a pool of port numbers. ![]() The services that are using TCP are each dynamically allocated their own TCP ports, The services may be using named pipes or TCP/IP. You can bind to that port on a remote computer anonymously and enumerate all the various RPC servicesĪvailable on that computer. A very brief summary of how the protocol works: There is an “endpoint mapper” that runs on TCP port 135.
0 Comments
Leave a Reply. |