Re: [Samba] idmap backend ad well-known-sids 512 & 513
- Date: Wed, 13 Feb 2019 16:57:58 +0000
- From: Rowland Penny via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] idmap backend ad well-known-sids 512 & 513
On Wed, 13 Feb 2019 17:26:05 +0100
"L.P.H. van Belle via samba" <samba@xxxxxxxxxxxxxxx> wrote:
> In addition to Rowland's.
> And be aware that there is a bug in
> unix_primary_group =
> You only see 10000 or Domain Users.
> If you change the primary groep to something else, it stays
> 10000/Domain users.
> default group always set to "Domain Users" not evaluating
> PrimaryGroupID ldap attribute
> You know that you have to set the UID/GID's yourself?
This isn't in my opinion a bug ;-)
Lets start with a Unix domain member that as 'unix_primary_group = yes'
rowland@devstation:~/mate$ getent passwd usertest
Here we can see that user 'usertest' has the group ID '10001', this is
the ID for a Unix group stored in AD.
Now we will go to a DC:
root@dc4:~# getent passwd usertest
The group ID is now '10000' and this is the gidNumber for 'Domain Users'
Finally, a Unix domain member using the 'rid' backend
adminuser@Computer4:~$ getent passwd usertest
The group id is now '10513', this is the RID for 'Domain Users' plus
the low range set in smb.conf, this is '10000'
So, one user, three group ID's
So, why do I not think it is a bug ?
If somebody logs into 'devstation' and has a gidNumber, they will get
the Unix primary group.
If somebody connects to a share, they are either connecting from a
Windows machine or a Samba machine that is 'simulating' a Windows
machine. In this case, Windows expects the users Primary group to be
In my opinion, you either never use the same username from a Windows
machine and Unix machines, or you always use 'Domain Users' as the
users primary group.
To unsubscribe from this list go to the following URL and read the