search for: base_rid

...needs a rewrite so a normal user can understand. Using a practical example. Step 1: determine the highest UID in use for your /etc/passwd file (can we assume everyone has a passwd file?) Step 2: I don't know... Optionally at this point, document how to plug that into the formula RID = ID + BASE_RID - LOW_RANGE_ID and then show how we set the lines: range = low - high base_rid = INTEGER The man page examples do not line up with any numbers practical outside of smb.conf Say my UID on the Linux side would never exceed 70000. How do I configure range and base_rid?

Okay, so I've now read 'man idmap_rid'. It states that the use of the base_rid parameter is deprecated, so does that change ID formula to this? ID = RID + LOW_RANGE_ID Assuming that the default value for the now-deprecated base_rid is 0. Following the example on the man page, I am going to try this: idmap config * : backend = tdb idmap config * :range = 1000000-1999999 i...

...te the manpage a bit, let me explain here: > Step 1: determine the highest UID in use for your /etc/passwd file > (can we assume everyone has a passwd file?) > Step 2: I don't know... > > Optionally at this point, document how to plug that into the formula > > RID = ID + BASE_RID - LOW_RANGE_ID > > and then show how we set the lines: > > range = low - high This 'low' here is the LOW_RANGE_ID referenced above in the formula. More concretely, this config would be idmap config DOMAIN : backend = rid idmap config DOMAIN : range = low-high > bas...

...AY nt acl support = yes vfs objects = acl_xattr winbind enum users = yes winbind enum groups = yes winbind offline logon = yes allow trusted domains = yes idmap config * : backend = rid idmap config * : range = 70000-99999 idmap config * : base_rid = 0 idmap config A : backend = rid idmap config A : range = 400000-499999 idmap config A : base_rid = 0 idmap config B : backend = rid idmap config B : range = 300000-399999 idmap config B : base_rid = 0

...d the mail about the new idmapping so i also tried these configuration: winbind enum users = yes winbind enum groups = yes allow trusted domains = yes idmap config A : backend = rid idmap config A : range = 100000 - 199999 idmap config A : base_rid = 1000 idmap config B : backend = rid idmap config B : range = 200000 - 299999 idmap config B : base_rid = 1000 With this configuration i get with "winbind -u" all users, but "getent passwd" is still empty. And a group group-info shows WBC_ERR_D...

...to see if the groups exist. >> > I don't understand how your users/groups changed their IDs, on the DC RIDs are mapped and stored in idmap.ldb, you are also using the winbind 'rid' backend and again, the user/group IDs are mapped from the RID by the algorithm: ID = RID - BASE_RID + LOW_RANGE_ID The BASE_RID is '0' so this becomes: ID = RID + LOW_RANGE_ID So unless you changed the range in smb.conf, your user/group IDs shouldn't change. I still don't understand where your private groups are coming from, unless, are you running sssd or nlscd as well as w...

...Users and computers (samba 4 AD DC) SID: S-1-5-21-XXXXXXXXXX-XXXXXXXXX-XXXXXXXXXX-5878 uidNumber : 10023 My actual config (in file-server) : idmap config XXXXXX:backend = ad idmap config XXXXXX:schema_mode = rfc2307 idmap config XXXXXX:range = 1005-40000 If I apply RID backend : ID = RID - BASE_RID + LOW_RANGE_ID. For the first account : 3216 - 0 + 1005 = 4221 => bad must be 1108 For the latest created account : 5878 - 0 + 1005 = 6883 => bad must be 10023 if generated uidNumber not the same that actual uidNumber, I will lose my ACL. regards Stéphane Purnelle De :...

...Linux Server release 7.6 (Maipo) Samba/Winbind Version 4.8.3 One issue I've been having is trying to get UIDs to coinside between old and new software versions. Our Samba 3 configs have the following defined: idmap config ADSMC:default = yes idmap config ADSMC:backend = rid idmap config ADSMC:base_rid=500 idmap config ADSMC:range = 2000-100000 I've set up the following in our Samba 4 server: idmap config ADSMC:range = 2000-100000 idmap config * :range = 2000-100000 idmap config ADSMC : backend = rid idmap config * : backend = tdb In an effort to keep things as compatible as possible betwee...

...derstand. Using a practical example. > > Step 1: determine the highest UID in use for your /etc/passwd file > (can we assume everyone has a passwd file?) > Step 2: I don't know... > > Optionally at this point, document how to plug that into the formula > > RID = ID + BASE_RID - LOW_RANGE_ID > > and then show how we set the lines: > > range = low - high > base_rid = INTEGER > > The man page examples do not line up with any numbers practical > outside of smb.conf > > Say my UID on the Linux side would never exceed 70000. How do I > co...

...; idmap config BUERO:backend = rid > idmap config BUERO:range = 10000-99999 > idmap config BUERO:schema_mode = rfc2307 Well, that explains where '11029' is coming from, you are using the 'rid' backend. The users (or group) ID will be calculated using this formula: ID = RID - BASE_RID + LOW_RANGE_ID BASE_RID is by default '0', so it becomes: ID = RID + LOW_RANGE_ID So, in your case it becomes 11029 = 1029 + 10000 Of course, using the 'rid' backend means that you do not need to add anything to AD and you do not need this line in smb.conf: idmap config BUER...

Hi Rowland, I haven't seen a base_rid parameter in his smb.cfg. That's why I advised to correct the value down to 1000 just to give it a try. I also had the problem of not getting any users with getent passwd with ad backend until I realized that all users must have a rfc2307 uid and must have a primary group in ad which also has...

...ins only = >> yes) and on Solaris and Linux samba machines of various verions. >> >> >> I also tried >> >> >> idmap config MYDOMAIN : backend = rid >> idmap config MYDOMAIN : range = 100-300 >> idmap config MYDOMAIN : base_rid = 0 >> >> >> >> but no luck. > > Not surprised really, the rid is calculated using this formula: > > ID = RID - BASE_RID + LOW_RANGE_ID. > > So, using the info you posted above: > > ID = 1234 - 0 + 100 > > Which becomes: > > ID = 1334 >...

Hi, I don't think that rid backend will work, because when we start samba (samab 2.2.8a) lower uid was 1000, but when we moved to samba 4, power uid was put to 10000. That's mean new user and group use uidNUmber or groupNUmber > 10000. But we have old account and group with uid or gid < 10000 regards Stéphane Purnelle "samba" <samba-bounces at

Hi, no, that's my fault. I changed the UIDs and user names in my "ls -l" to unpersonalized/example data for my mail and didn't think about putting these values into the range. A better unpersonalized data example would look like: ---------- drwx------ 43 DOM\user1        DOM\group  4096 Jan 10 08:00 user1 drwx------   5 DOM\user2        DOM\group  4096 Jan 11 08:13 user2

...g *:range = 2000-9999 idmap config * : backend = tdb # wbinfo --group-info=domänen-benutzer domänen-benutzer:x:10513: 2) winbind use default domain = Yes idmap config * : range = 10001-20000 idmap config domain : backend = rid idmap config domain : range = 10000-20000 idmap config domain : base_rid = 0 idmap config * : backend = tdb # wbinfo --group-info=domänen-benutzer domänen-benutzer:x:10008: I understand/assume that the different idmap configs might cause the mismatch in the mapped(?) groupids. Can I fix that without breaking things? On which server? ... oh my, I checked a 3rd one...

...34" shows the correct result and the "ls -l" list also > list the user name instead of the uid. > Please don't mess with the numbers, '10234' is still an invalid ID. You are using the 'rid' backend and this calculates the ID from the RID with: ID = RID - BASE_RID + LOW_RANGE_ID To calculate the RID from the ID, you would use: RID = ID + BASE_RID - LOW_RANGE_ID the 'BASE_RID' is always '0' (unless you set it) so the above becomes: RID = 10234 - 10000 RID = 234 Please post again with the CORRECT IDs, a number cannot be that secret ;-) R...

...ing. Any idea on why the *ad* back end does not > work ? As I said, it was only a test, it shows that there is connectivity to your AD DC, but the ID's are not what I expected. The 'rid' backend works by calculating the ID from the user or group RID It use this formula: ID = RID - BASE_RID + LOW_RANGE_ID The 'BASE_RID' defaults to '0', so it becomes: ID = RID + LOW_RANGE_ID The 'LOW_RANGE' is what is set in smb.conf: ID = RID - BASE_RID + 10000 So all the users and groups should be '10000' or above. Did you restart Samba and also run 'net cac...

>Your user has the RID 1581344 and the 'rid' backend uses this along >with the low range to calculate the users Unix ID, so from the commented >line, this would be: >79846 + 1581344 = 1661190 >This is less than the high range, so would be valid. >But if you use '100001-500000000' for the range, the ID would be: >100001 + 1581344 = 1681345 >This would

...this: cat /etc/passwd | grep 'qqeda11' Do you get something like this: qqeda11:x:79846:79846:qqeda11,,,:/home/qqeda11:/bin/bash If you do, then your user isn't an AD user. If you read 'man idmap_rid', you will find the calculation to map an AD user to a Unix ID: ID = RID - BASE_RID + LOW_RANGE_ID BASE_RID is usually 0 but you can set it to what you want WARNING, BOTCH AHEAD So, as you want the user to have the Unix ID 79846 and the user has the RID 1581344 in AD, you could set the low range to 0, this would end up with the calculation becoming: 79846 = 1581344 - 1501498...

...here: > > > Step 1: determine the highest UID in use for your /etc/passwd file > > (can we assume everyone has a passwd file?) > > Step 2: I don't know... > > > > Optionally at this point, document how to plug that into the formula > > > > RID = ID + BASE_RID - LOW_RANGE_ID > > > > and then show how we set the lines: > > > > range = low - high > > This 'low' here is the LOW_RANGE_ID referenced above > in the formula. More concretely, this config would be > > idmap config DOMAIN : backend = rid > id...