The client implementation has to have the network address of the server. This network address satisfies the requirements of a network address for the underlying transport of remote procedure call (RPC). This allows the client to initiate communication with the server by using the RPC Protocol.
This protocol uses security information as specified in [MS-RPCE]. The client and Exchange NSPI server are required to share one or both of the NT LAN Manager (NTLM) Authentication Protocol or Kerberossecurity providers (2) in common for the RPC transport. Additionally, the server is required to register the negotiation security provider (2).
The protocol does not require mutual authentication. The client and Exchange NSPI server use an authentication mechanism that is capable of authenticating the client to the server. The protocol does not require that the client be capable of authenticating the server.
The credentials of the client have to be recognized by the server. These credentials are obtained from the shared security provider (2). The mechanism for obtaining these credentials is specific to the protocol of the security provider (2) that is used.
The server has to be configured to support the required code pages and language code identifiers (LCIDs), as described in sections 2.2.4 and 2.2.5. This allows the server to provide the minimal required string conversions and sort orders.
The server has to be started and fully initialized before the protocol can start.