Lockouts caused by Samba

[Gray, Steven]

This problem was somewhat irregular in the past, but is becoming a major
nuisance now...

On connecting a drive, users (all W95) have their NT domain accounts locked
out. In the logs, I see things like:

[2000/02/09 07:24:49, 1] smbd/password.c:(1131)
  password server <PDC> rejected the password
[2000/02/09 07:24:49, 0] passdb/smbpass.c:(50)
  startsmbfilepwent: unable to open file /opt/samba/private/smbpasswd
[2000/02/09 07:24:49, 0] passdb/passdb.c:(149)
  unable to open smb password database.
[2000/02/09 07:24:49, 1] smbd/password.c:(504)
  Couldn't find user '<userid>' in smb_passwd file.

(I put in the <PDC> and <userid> thingies)

I am running 2.0.4b on a Sun E-450 with Solaris 2.6.

The pertinent smb.conf settings:

   security = server
   password server = <PDC1>,<PDC2>,<PDC3>
   wins server = nnn.nnn.nnn.nnn (IP of primary WINS server)
   local master = no

I also have the socket address specifically set, with "bind interfaces only
= yes" and "interfaces" set to a specific IP address, since I am running
multiple IP addresses on a single interface.

My guess as to what's happening:

1. Samba passes the userid/bad_pw combo to the domain controller, and it
fails, as expected. Strike 1.
2. Samba mangles the correct password and/or the 95 client pulls some
incorrect data from the local .pwl file. Strike 2.
3. Either the user re-types the password, or hits "Cancel" and the client
proceeds to the next drive. Either way, Step 1 is repeated, and the account
is at Strike 3, and the user is locked out.

Is there some known way around this? This is becoming a critical problem,
since it's effecting my users' work, and my mental well being... 8-)

(I have the 2.0.6 binary distribution ready to install, but I haven't done
it yet, in case it might help.)


______________
Steve Gray
Engineering Practices and Standards (EPS), TycoElectronics Corp.
sagray at tycoelectronics.com