Updated: December 3, 2008
Applies To: Windows Server 2008 R2
Remote procedure call (RPC) is a standard that enables one process to make calls to functions that are executed in another process. The processes can be on the same computer or on different computers in a network.
The following is a list of the managed entities that are included in this managed entity:
The Remote Procedure Call (RPC) service (RpcSs) listens on a set of the computer's network interfaces. Using RPC Firewall Filters, an administrator can control the network interfaces that RpcSs is allowed to listen on. The administrator can use RPC Firewall Filters to block some interfaces from being accessed over a given network interface while allowing other interfaces to be accessed over the same network interface. RPC Firewall Filters make it possible for the administrator to configure network interface access on a per-interface level of detail.
Remote procedure call (RPC) clients can use RPC over Hypertext Transfer Protocol (HTTP) to connect securely and efficiently across the Internet to RPC server programs and to execute remote procedure calls.
RPC over HTTP Proxy is a proxy that is used by objects that receive remote procedure calls over HTTP. Clients can use this proxy to discover these objects even if the objects are moved between servers or if they exist in discrete areas of the network, usually for security reasons.
The RPC over HTTP Proxy runs on an Internet Information Services (IIS) computer. It accepts RPC requests coming from the Internet, and it performs authentication, validation, and access checks on those requests. If a request passes all the tests, the RPC over HTTP Proxy forwards the request to the RPC server that performs the actual processing. With RPC over HTTP, the RPC client and server do not communicate directly. Instead, they use the RPC over HTTP Proxy as an intermediary.