If you are getting UID/GIDs mapped above 32768 then you are just using the default builtin usermapper.  If you want “static” mapping from AD or other sources you need to specifically configure this.  Please see the CIFS and Name services manuals.  Rainer
Situation: Win2K domain with several hundred users / groups. There is an existing (older) EMC device (unknown model) that is used for home directories. It has CIFS shares and exports NFS mount points for each share. All user account info is set via MMC snapin on primary domain controller.  We got an NX4 recently and set it up as a secondary file share device. The hope was that we could use it for CIFS and NFS as well.  CIFS is working fine but the UID/GID info is not being inherited from the AD domain properly. All accounts are getting new values from 32768 and rising.   Expectation: that the AD values for UID / GID would be picked up by the new device when it joined the domain.  I used 'server_cifssupport' to get the lists from both old and new machines. On the old machine I see the expected account info with 'nis' or 'active directory' listed as the source. On the new machine I see only a few accounts and each has 'usermapper' listed.   I looked at the usermapper service on the new machine: bin/server_usermapper server_2 server_2 : Usrmapper service: Initialized Service Class: Primary  Sounds like its trying to run so I disabled it. This didn't seem to have any effect on the list from 'server_cifssupport'.   Looking at the same value on the old machine I see:  server_2 : Usrmapper service: Uninitialized  So it looks like I want to revert the new system to this 'uninitialized' state. How? Is this even the correct approach? Do I want to delete everything from the 'usermapper' as well?  Am I headed down the wrong track altogether?
Mapping UIDs to new NX4 from existing EMC device