search for: user_in_winbind_group_list

Hi All Folks, RH7.3 I could not start 'swat' on Konsole window # swat - It hanged there. I also tried after having Samba started with the same result # rpm -qa | grep samba-swat samba-swat-2.2.3a-6 It was there. I have re-installed it from RH CD with no improvement Kindly help Stephen Liu

First, i'm sorry to be so silly that i don't even to success a basic samba configuration simply working. Compilation of the rc2 had no errors. testparm against my smb.conf said ok, and i can start nmbd and smbd. I also add a new unix user, said toto, and added it in samba. The problem is that i can't connect to any share, via Windows or via GNU/Linux. The result from Windows is a new

.../21 17:16:44, 10] lib/username.c:user_in_list(533) user_in_list: checking user |WW300+atw113c9| against |ww300+csi| [2004/10/21 17:16:44, 10] lib/username.c:user_in_list(610) user_in_list: checking if user |WW300+atw113c9| is in winbind group |ww300+csi| [2004/10/21 17:16:49, 10] lib/username.c:user_in_winbind_group_list(412) user_in_winbind_group_list: using groups -- 30001 30002 30003 30004 30005 30006 30007 30008 30009 300 10 30011 30012 30013 30014 30015 30016 [2004/10/21 17:16:49, 2] smbd/service.c:make_connection_snum(314) user 'WW300+atw113c9' (from session setup) not permitted to access this sha...

...rname.c:user_in_list(533) > user_in_list: checking user |WW300+atw113c9| against |ww300+csi| > [2004/10/21 17:16:44, 10] lib/username.c:user_in_list(610) > user_in_list: checking if user |WW300+atw113c9| is in winbind group > |ww300+csi| > [2004/10/21 17:16:49, 10] lib/username.c:user_in_winbind_group_list(412) > user_in_winbind_group_list: using groups -- 30001 30002 30003 30004 > 30005 30006 30007 30008 30009 300 > 10 30011 30012 30013 30014 30015 30016 > [2004/10/21 17:16:49, 2] smbd/service.c:make_connection_snum(314) > user 'WW300+atw113c9' (from session setup) not per...

...encounters the problem, going into "Network Neighborhood" -> SambaServer - -> username will allow access to the share, AND returning to the F: mapping it then works fine. Checking the logs, all of the users who are losing their mappings have the following error: lib/username.c:user_in_winbind_group_list(357) user_in_winbind_group_list: winbind_lookup_name for group jsmith failed. where jsmith is their username, and no such group has ever existed. Also, there are users receiving this error who are not losing their mappings. Here is the pertinent section from smb.conf ### Winbind settings wi...

...or domain 'PROSADOM Jan 27 11:03:25 wanda winbindd[1015]: [2003/01/27 11:03:25, 0] nsswitch/winbindd_group.c:winbindd_getgrnam(210) Jan 27 11:03:25 wanda winbindd[1015]: could not get domain sid for domain 'PROSADOM Jan 27 11:03:25 wanda smbd[1492]: [2003/01/27 11:03:25, 0] lib/username.c:user_in_winbind_group_list(356) Jan 27 11:03:25 wanda smbd[1492]: user_in_winbind_group_list: winbind_lookup_name for group 'PROSADOM+Domain failed. Jan 27 11:03:25 wanda winbindd[1015]: [2003/01/27 11:03:25, 0] nsswitch/winbindd_group.c:winbindd_getgrnam(210) Jan 27 11:03:25 wanda winbindd[1015]: could not get domai...

Hi, Installed latest Samba3.0.2a on NT4 domain, security = domain and net rpc join successfully. everything work great, but group permission failed, error message is "user_in_winbind_group_list: nametogid for group NTGROUP failed". smb.conf on shares as below: ===================== omitted base configurations... [shareA] path = /public/shareA valid users = <mailto:'@NT\Domain> '@NT\Domain Users' write list = NT\steven the conf is simple but error occured....

...g Subject: Re: [Samba] group problem on NT4 domain On Tue, 17 Feb 2004, steven.TSE wrote: > Hi, > > Installed latest Samba3.0.2a on NT4 domain, security = domain and net rpc > join successfully. > > everything work great, but group permission failed, error message is > "user_in_winbind_group_list: nametogid for group NTGROUP failed". Do you have winbindd running? Is /etc/nsswitch.conf configured to use winbind? - John T. > > smb.conf on shares as below: > ===================== > omitted base configurations... > > [shareA] > path = /public/shareA > valid users...