Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell PowerStore Configuring Multiprotocol File Sharing

PDF

SID to UID and primary GID mapping

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

  1. secmap is searched for the SID. If the SID is found, the UID and primary GID mappings are resolved.
  2. If the SID is not found in secmap, the Windows username that is related to the SID must be found.
    1. The local group database (LGDB) is searched for the SID to determine if the user is local. If the SID is found, the related Windows name is SMB_SERVER\USER. Since it is a local user for SMB-only access, no UNIX mapping is required.
    2. If the SID is not found in the LGDB, the DC of the domain is searched. If the SID is found in the domain, the related Windows name is DOMAIN\USER.
    3. If the SID cannot be resolved, access is denied. The failed mapping is added to the persistent secmap database.
  3. If the default UNIX account is not used, the Windows name is translated to the UNIX name using ntxmap.
    1. If the Windows name is found in ntxmap, the entry is used as the UNIX name.
    2. If the Windows name is not found in ntxmap, or if ntxmap is disabled, the Windows name is used as the UNIX name.
  4. The local files or UDS is searched using the UNIX name to find the UID and primary GID.
    1. If the UNIX username is found, the UID and primary GID mapping is resolved. The successful mapping is added to the persistent secmap database.
    2. If the UNIX username is not found, but the automatic mapping for unmapped Windows accounts feature is enabled, the UID is automatically assigned. The successful mapping is added to the persistent secmap database.
    3. If the UNIX username is not found, but a default UNIX account, the UID and primary GID mapping are mapped to that of the default UNIX account. The failed mapping is added to the persistent secmap database.
    4. If the UNIX username cannot be resolved, access is denied. The failed mapping is added to the persistent secmap database.

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 an SID to a UID, primary GID mapping:

Figure 1. Process for resolving an SID to a UID, primary GID mapping
Process for resolving an SID to a UID, primary GID mapping

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\