A File Server machine must have an RPC binding in CDS for its DCE path name. The fts program uses the RPC binding to contact the File Server machine when it needs to communicate with the ftserver process on the machine. This RPC binding includes the server machine's network address, an identifier for the protocol used to communicate with the machine, and an endpoint for communications with the endpoint mapper service of the dced process on the machine.
In DCE, server machines are identified by DCE path names of the form /.../cellname/hosts/hostname; for example, /.../abc.com/hosts/fs1. The entry in CDS for the RPC binding defined for each server machine must have a name of the form /.../cellname/hosts/hostname/self; for example, /.../abc.com/hosts/fs1/self.
Note that the DFS server principal for the machine is similarly derived. The abbreviated server principal registered for the machine in the FLDB is similar in form to the RPC binding and DFS server principal.
Note: The element that follows the cellname in the path name is not well known; for example, hosts could be dfs-hosts. However, the string used for the element must be applied consistently to all such names in the cell.
To create an RPC binding for a File Server machine, use the dcecp command to create the structure for the RPC binding in CDS. The entry for the RPC binding in CDS must have a name of the form /.../cellname/hosts/hostname/self.