Login problems after upgrade

Jens B. Jorgensen jjorgens at bdsinc.com
Fri Aug 13 19:08:07 GMT 1999


Take a look at /var/log/smb. Do you see:

[1999/07/02 10:00:55, 0] smbd/uid.c:become_gid(105)
  Couldn't set effective gid to 100 currently set to (real=0,eff=0)
[1999/07/02 10:00:55, 0] smbd/service.c:make_connection(425)
  Can't become connected user!

Then the problem is that the version you're installing is compiled to use
the system calls setreuid/setregid. These calls seem to exist in 2.0.X but
they do not work. Trouble is even if you compile the source yourself, the
configure script will think it can use these calls. You have to manually fix
it so these calls aren't used. That's what I did and I've got binaries up on
my work home page:

http://gatekeeper.bdsinc.com/~jjorgens/debian

They're debian packages but a debian package is just an ar archive which has
tar.gz's embedded in it so it shouldn't be too hard to extract what you
want.

John Rooke wrote:

> Hi,
>
> I have just upgraded Samba on our Linux box from samba-2.0.2-20.i386.rpm
> to samba-2.0.5a-0.i386.rpm and are using the same smb.conf and sbpasswd
> files that worked with 2.0.2. Now when I try to login using the new
> version I get the following:
>
> saturn:/etc # smbclient -L
> saturn
> Added interface ip=10.1.1.13 bcast=10.1.1.255
> nmask=255.255.255.0
> Password:
> Domain=[LPTEST] OS=[Unix] Server=[Samba
> 2.0.5a]
> tree connect failed: ERRSRV - ERRbadpw (Bad password - name/password
> pair in a Tree Connect or Session Setup are
> invalid.)
> saturn:/etc #
>
> All other samba tools seem to report everything is OK e.g. smbpasswd,
> swat, smbstatus all wortk OK.
>
> As soon as I re-install 2.0.2 I am OK again.
>
> We are using SuSE Linux 6.0 with the 2.0.36 kernel if that hapls.
>
> Any pointers on what I need to do would be very much appreciated.
>
> Thanks,
>
> --
> John Rooke
> Director
> L&P Systems Limited
> john.rooke at lpsystems.com

--
Jens B. Jorgensen
jjorgens at bdsinc.com




More information about the samba-ntdom mailing list