Share via

Remote Procedure Calls

  • Article

If you have applications that utilize Remote Procedure Calls (RPC), you might need to include multiple RPC components in your configuration. If an RPC function is called, but the RPC component exposing that function is not installed, the function call fails.

The following table shows the available RPC components.

Component Description
RPC Local Support Facilitates local RPC using the ncalrpc and ncacn_np protocol sequences, and provides support for dynamic endpoint resolution.

RPCs using the ncalrp protocol can enhance security for remote procedure calls without the need for additional RPC components.
RPC Remote Facilitates local and remote RPC calls using the ncacn_ip_tcp, ncacn_http, and ncadg_ip_udp protocol sequences. This component provides the following client and server RPC functionality:
  • ncacn_ip_tcp
  • ncadg_ip_udp
  • ncacn_http, which requires an RPC proxy computer

Secure RPCs are not facilitated by the RPC Remote component. At least one RPC Secure component is required to make secure RPCs, such as Secure RPC over Kerberos, Secure RPC over Negotiate, Secure RPC over NTLM, or Secure RPC over SSL.

The RPC Remote component includes the functionality provided in the RPC Local Support component. Therefore, if you include RPC Remote in a configuration you do not need to include the RPC Local Support component.
RPC Authorization Support Exposes the RpcGetAuthorizationContextForClient and RpcFreeAuthorizationContext functions. The RPC Authorization Support component provides no other RPC functionality, and is necessary only to obtain the RPC capabilities exposed by the specified functions.
RPC HTTP CIS Server Provides the RPC proxy necessary to make RPC HTTP calls, and is also required by CIS. To successfully complete an RPC over HTTP RPC, the following components must be installed: the RPC Remote component must be installed on the client, the RPC HTTP CIS Server component must be installed on the proxy machine, and the RPC Remote component must be installed on the server.
RPC Named Service Provides RPC named service functionality, such as the RPC Locator. The RPC Named Service component exposes all RpcNsxxx RPC functions.

The RPC Named Service component includes RPC Locator service functionality, which runs on the local machine and on the domain controller. The RPC Named Service component is typically used by applications using the auto_handle attribute.
RPC Remote over Named Pipes Facilitates remote procedure calls using the ncacn_np protocol sequence. RPC over Named Pipes to a server on the same computer requires the RPC Local Support component.
RPC Remote over SPX Facilitates RPCs over SPX to servers residing on the local computer or a remote computer The RPC Remote over SPX component includes both client and server support, and includes support for SPX name resolution.
Secure RPC over Kerberos Facilitates RPCs using the Kerberos Security Support Provider Interface (SSPI) for authentication and privacy protection.
Secure RPC over Negotiate Facilitates RPCs using the Negotiate Provider Interface SSPI for authentication and privacy protection. This component is not required to make non-secured RPCs. Other Secure RPC components provide different SSPI capabilities for RPC; developers generally include one or more Secure RPC components to secure RPCs.
Secure RPC over NTLM Facilitates RPCs using the Windows NT Challenge/Response (NTLM) SSPI for authentication and privacy protection.
Secure RPC over SSL Facilitates making remote procedure calls using the SChannel SSPI for authentication and privacy protection. This component is not required to make non-secured RPCs. Other Secure RPC components provide different SSPI capabilities for RPC; developers generally include one or more Secure RPC components to secure RPCs.

See Also

Manage and Service a Run-Time Image

Last updated on Wednesday, October 18, 2006

© 2006 Microsoft Corporation. All rights reserved.