search for: mssfu30gidnumber

...AD domain using windbind, and define on the smb.conf "idmap gid = 10000-20000". I logged in using my AD user account, and when I'm doing "id", I see that all the AD groups GID start at 10000. How can I define that groups GID will be exactly like on my AD? (The "msSFU30GidNumber" attribute) Why the "id" commands show only the first 32 groups? And how can I see more then 32? Thanks In Advanced! Nir B

...ally, it added uid, gid, shell, and home directory objects, plus a nice new tab called UNIX Attributes to the user properties window of the Active Directory Users and Computers MMC. So for instance, something like this should be an option in smb.conf: winbind uid = msSFU30UidNumber winbind gid = msSFU30GidNumber (this would denote the users Primary group name) winbind shell = msSFU30LoginShell winbind home = msSFU30HomeDirectory The people who use AD4Unix could change these variables to whatever it creates. Anyway, it seems like a much more simple way to get the uid's and gid's to be the same...

...> [root@io source]# > > ===================================== > > I have lots of messages of this in winbindd.log: > > [2006/04/21 12:01:13, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(329) > ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute > 'msSFU30GidNumber' > [2006/04/21 12:01:13, 1] > nsswitch/winbindd_user.c:winbindd_fill_pwent(92) > error getting group id for sid > S-1-5-21-1663660479-371685239-1594628879-513 > > But I think thats not the problem because in winbindd_idmap.tdb are > all users with correct mappings that...

...out the line "idmap backend = ad:ldap://<PDC's FQDN>/" in smb.conf, I can successfully do all of: #> wbinfo -S $(wbinfo -n some_user | awk '{print $1}')" #> getent passwd | grep some_user #> net ads search '(objectCategory=user)' \ sAMAccountName msSFU30GidNumber msSFU30UidNumber | \ grep -A2 some_user However, if I add the line "idmap backend = ad:ldap://<PDC's FQDN>/" to smb.conf and I do: #> wbinfo -S $(wbinfo -n some_user | awk '{print $1}')" I get the following error: "Could not convert sid <sid of some_u...

with samba 3.0.22, I'm trying to integrate a linux box with Microsoft AD by using winbind for authentication as well as for the source of nss info. When winbind is configured to use its own local id maps, everything works fine. But when i configure winbind to use 'ad' as the source of nss info, authentication fails, 'getent' commands return no results, and 'wbinfo -r

...e). Because nss_ldap is reported broken with dovecot I'm trying to use dovecot-ldap for both passdb and userdb. My guessed filters/attributes follows: user_filter = (&(objectClass=user)(msSFU30Name=%u)) user_attrs = homeDirectory=msSFU30HomeDirectory, uidNumber=msSFU30UidNumber, gidNumber=msSFU30GidNumber pass_attrs = msSFU30Name,msSFU30Password pass_filter = (&(objectClass=user)(msSFU30Name=%u)) But it doesn't work. Any advice? Cristian Salan

...in/nologin ntp:x:38:38::/etc/ntp:/sbin/nologin [root@io source]# ===================================== I have lots of messages of this in winbindd.log: [2006/04/21 12:01:13, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(329) ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute 'msSFU30GidNumber' [2006/04/21 12:01:13, 1] nsswitch/winbindd_user.c:winbindd_fill_pwent(92) error getting group id for sid S-1-5-21-1663660479-371685239-1594628879-513 But I think thats not the problem because in winbindd_idmap.tdb are all users with correct mappings that have the field msSFU30GidNumber. ==...

....c:winbindd_fill_pwent(92) error getting group id for sid S-1-5-21-3961909960-354130599-1050854057-513 [2009/07/16 16:01:15, 1] winbindd/winbindd_user.c:winbindd_getpwent(766) could not lookup domain user truth I have a tcpdump, and it shows that the query it's performing is returning the msSFU30GidNumber attribute (value 11). I'm unsure why it's unable to locate my group ID. I also have created a group with that same ID in Active Directory. The configuration I'm using to get the above results is as follows: idmap domains = default BLUE idmap config BLUE:backend = ad idmap config BLUE:...

...d=1.2.840.113556.1.6.18.1.344)(attributeId=1.2.840.113556.1.6.18.1.312)(attributeId=1.2.840.113556.1.6.18.1.337)) in <CN=Schema,CN=Configuration,DC=domain,DC=fi> gave 5 replies OID 1.2.840.113556.1.6.18.1.310 has name: msSFU30UidNumber OID 1.2.840.113556.1.6.18.1.311 has name: msSFU30GidNumber OID 1.2.840.113556.1.6.18.1.312 has name: msSFU30LoginShell OID 1.2.840.113556.1.6.18.1.337 has name: msSFU30Gecos OID 1.2.840.113556.1.6.18.1.344 has name: msSFU30HomeDirectory [2009/03/23 21:06:34, 0] lib/fault.c:fault_report(40) ========================================...