> > OK - I've looked at it again. The current code functions correctly, but > only lists groups that are 'mapped' with the smbgroupedit tool. > > Read the 'group-mapping-howto' in textdocs. I read that first... I've already mapped some unix groups. smbgroupedit -s says:
NT group (SID) -> Unix group System Operators (S-1-5-32-549) -> -1 Domain Users (S-1-5-21-1995982474-3671514283-3045899775-513) -> -1 Replicators (S-1-5-32-552) -> -1 Guests (S-1-5-32-546) -> -1 Power Users (S-1-5-32-547) -> -1 Print Operators (S-1-5-32-550) -> -1 Administrators (S-1-5-32-544) -> -1 power_users (S-1-5-21-1995982474-3671514283-3045899775-1401) -> power_users Domain Admins (S-1-5-21-1995982474-3671514283-3045899775-512) -> power_users Domain Guests (S-1-5-21-1995982474-3671514283-3045899775-514) -> -1 Account Operators (S-1-5-32-548) -> -1 Backup Operators (S-1-5-32-551) -> -1 Users (S-1-5-32-545) -> -1 power_users has members unheq1:/var/log/samba# groups khartman khartman : labusers power_users I'm using the ldap_nua backend if that matters rpcclient $> enumdomgroups result was NT_STATUS_UNSUCCESSFUL and I'm not able to see any groups when i use the XP select users or groups tool (i can see all the users) I'm sloooowly working my way through the code and adding more debug prints to try to figure out what is up here. I wish I could use gdb to do this... thanks for looking into it... by the way - this did work for me a while ago (before the printing merger from 2.2) i've also tried a18 without success. brad
