Hi. I have installed samba before. This time I cannot even do a smbclient -L localhost. When I try to connect I get that log: [1999/03/15 11:37:32, 0] smbd/uid.c:become_gid(105) Couldn't set effective gid to 408 currently set to (real=0,eff=0) [1999/03/15 11:37:32, 0] smbd/service.c:make_connection(425) Can't become connected user! [1999/03/15 11:37:50, 0] smbd/uid.c:become_gid(105) Couldn't set effective gid to 0 currently set to (real=0,eff=0) [1999/03/15 11:37:50, 0] smbd/service.c:make_connection(425) Can't become connected user! I searched the archives unsuccessfully. What am I missing ? thank you.
Hi Francesc I had a similar problem for some days ago when I tried to connect to a machine, running samba2.0.3 and RH52 with the original 2.0.36 kernel, in my domain by using smbclient. The problem was that samba used some c functions called setresgid and setresegid. These functions gave the error signal no matter what input I gave them. But i discovered that switching to kernel 2.2.3 solved my problem. Try looking in the sourcefile uid.c and find what functions you are using and see what output they give you. Inge Francesc Guasch wrote:> > Hi. I have installed samba before. This time I cannot even do > a smbclient -L localhost. When I try to connect I get > that log: > > [1999/03/15 11:37:32, 0] smbd/uid.c:become_gid(105) > Couldn't set effective gid to 408 currently set to (real=0,eff=0) > [1999/03/15 11:37:32, 0] smbd/service.c:make_connection(425) > Can't become connected user! > [1999/03/15 11:37:50, 0] smbd/uid.c:become_gid(105) > Couldn't set effective gid to 0 currently set to (real=0,eff=0) > [1999/03/15 11:37:50, 0] smbd/service.c:make_connection(425) > Can't become connected user! > > I searched the archives unsuccessfully. What am I missing ? > thank you.
Hi, Recently I got came up against a difficult problem with a stock Debian hamm install (kernel 2.0.34) and Samba 2.0.x (from Debian slink). Despite my best efforts, smbd refused to authenticate any valid user or allow guest login. (For guest, it suggested that my OS couldn't cope with UID's >65534 and for regular users it said it was unable to become user.) I'd tested thoroughly with a Win98 client I have to set up, and the Linux boxes via smbclient; neither was able to connect via guest or registered user logins. The Win98 client simply gave "Incorrect password - try again", while smbclient gave badpassword messages. This was both with encrypted passwords via smbpasswd, and with unencrypted. Upgrading to Linux kernel 2.2.10 fixed this, as per an earlier post by Inge-Haavard Hunstad at - http://us1.samba.org/listproc/samba/March1999/0370.html Thanks to the Samba team! Hope this info helps someone else who faces the same beastie ;) Cheers, Chris -- chris burgess http://ibex.co.nz