search for: ads_pull_uint32

...ere is an ubuntu package for 3.0.25. Any suggestions would be appreciated. Wbinfo -u and -g appear to work great. Net ads testjoin comes back successful. In log.winbindd-idmap I get a lot of these [2007/06/26 20:09:13, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(309) ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute 'gidNumber' [2007/06/26 20:09:13, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(309) ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute 'gidNumber' [2007/06/26 20:09:13, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(309) ad_idmap_get_id_from_...

...ed the winbind nss info = sfu. Nothing happened initially in the log.winbindd-idmap, but after lunch I saw some new things in there: 83390]: sid to uid S-1-5-21-54348060-1989963526-242692186-2762 [2006/08/25 14:07:22, 1] ../sam/idmap_ad.c:ad_idmap_get_id_from_sid(309) ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute 'uidNumber' [2006/08/25 14:07:22, 3] ../nsswitch/winbindd_async.c:winbindd_dual_sid2uid(201) [483390]: sid to uid S-1-5-21-54348060-1989963526-242692186-2762 [2006/08/25 14:07:22, 1] ../sam/idmap_ad.c:ad_idmap_get_id_from_sid(309) ad_idmap_get_id_from_sid: ads_...

.... If I use "idmap backend = ad" i can see in the logfile that it gets my uidNumber: ad_idmap_get_id_from_sid mapped SID [S-mysid] to POSIX UID myuid but it is not able to get my gidNumber: [2007/10/04 09:44:17, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(309) ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute 'gidNumber' any idea? thanks!

...ld_error(ENUM_ADS_ERROR_LDAP, rc, 0) ^~ ../libgpo/pygpo.c:354:12: note: in expansion of macro ‘ADS_ERROR’ status = ADS_ERROR(LDAP_NO_MEMORY); ^~~~~~~~~ ../libgpo/pygpo.c:358:7: warning: implicit declaration of function ‘ads_pull_uint32’; did you mean ‘ndr_pull_uint32’? [-Wimplicit-function-declaration] if (!ads_pull_uint32(ads, res, "userAccountControl", &uac)) { ^~~~~~~~~~~~~~~ ndr_pull_uint32 In file included from ../source3/include/ads.h:9:0, from ../libgpo/gpo.h:23,...

...samba configured to use ad as the idmap backend, and sfu for nss info. When running getent passwd, only a few active directory users show up, and I get lots of errors like this in my winbind log: [2006/10/20 15:33:49, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(309) ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute 'msSFU30UidNumber' [2006/10/20 15:33:49, 1] nsswitch/winbindd_user.c:winbindd_fill_pwent(85) error getting user id for sid S-1-5-21-1020778807-1917943211-1564386419-1158 [2006/10/20 15:33:49, 1] nsswitch/winbindd_user.c:winbindd_getpwent(711) could not lookup do...

I have Samba 3.0.7 installed and running in security = ADS mode and I've built and installed the Idmap_ad backend according to the instructions. Group lookups seem to work fine, but getent passwd and id functions fail with the message - ad_idmap_get_id_from_sid: ads_pull_uint32 : could not read attribute 'gidNumber'. If I manually run an ldap query against Active Directory the attribute shows up just fine in either root's or a user's context using GSSAPI. I've extended the AD schema using MKSADplugins and I'm using the RFC2307 schema style. Any su...

...p.tdb): rec_read bad magic 0x42424242 at offset=20784688 [2006/01/23 06:44:32, 0] tdb/tdbutil.c:tdb_log(772) tdb(/var/lib/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=20784688 [2006/01/23 06:44:32, 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 'uidNumber' [2006/01/23 06:44:32, 1] nsswitch/winbindd_user.c:winbindd_fill_pwent(85) error getting user id for sid S-1-5-21-2000478354-789336058-725345543-115409 Here is my smb.conf details: [global] workgroup = DOM realm = DOM.COM se...

...g: Sid S-1-5-32-544 -> BUILTIN\Administrators(4) zebra.log: create_local_nt_token: Failed to create BUILTIN\Administrators group! I am also getting the following in the log.winbindd-idmap file. [2006/07/18 11:41:33, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(314) ad_idmap_get_id_from_sid: ads_pull_uint32: could not read attribute 'gidNumber' I have gidNumber defined for all Unix users and all of their groups and this has been working fine until now. I can access the user homedrive OK, but this failure is occuring when I try to access a share protected by the group access declaration .....

...nologin postfix:x:89:89::/var/spool/postfix:/sbin/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 ma...

...sbin/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_idm...

First thing - I'd like to say a big "THANK YOU" to the developers. I just upgraded to samba-3.0.23 and I've noticed an alarming issue with respect to my configuration. I've been using the built-in keytab management and it looks like the updated code no longer creates the userPrincipal in Active Directory. Whether this is an issue for others or not, it would be nice to have