2.1.5 Protocol Relationship

The following diagram shows the protocol layering relationships for the File Services Management system member protocols that use remote procedure call (RPC) as a transport.

Protocol relationship of RPC-related protocols

Figure 3: Protocol relationship of RPC-related protocols

The protocols [MS-DFSNM], [MS-SRVS], and [MS-WKST]  use [MS-RPCE] over named pipes. Thus, the protocols can be transported over SMB access protocols and cannot use any of the other RPC transports. The File Server Resource Manager Protocol, as described in [MS-FSRM], [MS-DFSRH], [MS-FRS1], and [MS-FRS2], uses the Remote Procedure Call Protocol Extensions over TCP only. For more information on the type of RPC transport, see section 2.10.

The following diagram shows the protocol layering relationships of the Remote Administration Protocol [MS-RAP].

Protocol relationship of the Remote Administration Protocol

Figure 4: Protocol relationship of the Remote Administration Protocol

The Remote Administration Protocol [MS-RAP] is an administrative protocol that is transported by the Common Internet File System (CIFS) and the Server Message Block (SMB) Protocol, but not by the Server Message Block (SMB) Protocol Versions 2 and 3 [MS-SMB2]. The function of the Remote Administration Protocol, as described in [MS-RAP], has largely been replaced by newer protocols. In the File Services Management system, the Remote Administration Protocol is used as a discovery protocol. File Services clients can discover servers by using the Remote Administration Protocol to retrieve a list of servers from the Browser Service, as described in the Common Internet File System (CIFS) Browser Protocol [MS-BRWS]. The Remote Administration Protocol also supports certain client and server administration methods, such as SMB file share enumeration, but this functionality has been superseded by the Workstation Service Remote Protocol [MS-WKST] and the Server Service Remote Protocol [MS-SRVS].