A File Server machine must also have a DFS server principal and associated account in the local Registry Database. The DFS server principal name is used to establish an authenticated connection to the DFS server machine.
In DCE, server machines are identified by DCE path names of the form /.../cellname/hosts/hostname; for example, /.../abc.com/hosts/fs1. The DFS server principal is of the form /.../cellname/hosts/hostname/dfs-server; for example, /.../abc.com/hosts/fs1/dfs-server. A machine's DFS server principal is similar in appearance to the name of its RPC binding, the difference being that the last element of the RPC binding name is self, whereas the corresponding element of the DFS server principal is dfs-server. The two elements also differ in that the RPC binding is defined in CDS, while the DFS server principal is registered in the Registry Database. Note again that hosts is not a well-known element of the name.
An abbreviation of the DFS server principal registered in the Registry Database must be used as the principal name associated with the machine's entry in the FLDB. Continuing with the previous example, hosts/fs1 is the abbreviated DFS server principal associated with the FLDB entry for the machine whose DFS server principal in the Registry Database is /.../abc.com/hosts/fs1/dfs-server. (The full DFS principal name of a server machine is also associated with a server encryption key in a keytab file; see Using Administrative Lists and Keytab Files for more information on server encryption keys.)
Use the dcecp principal create command to create a DFS server principal and associated account in the Registry Database for the File Server machine from which aggregates and partitions are to be exported. The DFS server principal must be of the form /.../cellname/hosts/hostname/dfs-server.