3.1.4.7 Calling Methods Not Requiring Session-Key Establishment

  • Article

The client follows this sequence of steps:

  1. The client SHOULD bind to the RPC server over TCP/IP  but MAY<82> use the named pipe "\PIPE\NETLOGON".

    Note The TCP/IP channel cannot support impersonation for access control and is therefore unusable. The server will ignore any calls made via this channel.

  2. The client calls the method on the server.

  3. The client unbinds from the server or reuses the binding for multiple RPC calls.