Dell PowerStore Configuring Multiprotocol File Sharing

The following sequence is the process that is used to resolve a UID to an SID mapping:

1. secmap is searched for the UID. If the UID is found, the SID mapping is resolved.
2. If the UID is not found in secmap, the UNIX name that is related to the UID must be found.
   1. Local files or the UDS is searched for the UID. If the UID is found, the related UNIX name is the username.
   2. If the UID is not found in the UDS but there is a default Windows account, the UID is mapped to the default Windows account. If it does not exist, the default Windows user is added to the persistent secmap database.
   3. If the UID is not resolved, access is denied.
3. If the default Windows account is not used, the UNIX name is translated into a Windows name, using ntxmap.
   1. If the UNIX name is found in ntxmap, the entry is used as the Windows name.
   2. If the UNIX name is not found in ntxmap, or if ntxmap is disabled, the UNIX name is used as the Windows name.
4. The DC or LGDB is searched for the Windows name to find the SID.
   1. The Windows name is searched for the DC. If the Windows name is found, the SID mapping is resolved.
   2. If the Windows name contains a period (.), and the part of the name following the last period matches an SMB server name, the LGDB of that SMB server is searched to resolve the SID mapping. If the Windows name is found, the SID mapping is resolved.
   3. If the Windows name is not found but there is a default Windows account, the SID is mapped to that of the default Windows account. If it does not exist, the default Windows user is added to the persistent secmap database.
   4. If the Windows name cannot be resolved, access is denied.

If the mapping is found, it is added in the persistent secmap database. If the mapping is not found, the failed mapping is added to the persistent secmap database.

The following diagram illustrates the process that is used to resolve a UID to an SID mapping: