yes, secuirty=server is not a good option, it keeps your auth connection even after auth is done, so thats the reason prob after a while password serer was rejecting users, you should monitor your windows password server as to what it is doing
-----Original Message----- From: Bradley W. Langhorst [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 11:13 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Samba] ClearCase and Samba security=SERVER is fraught with troubles... have you considered using security=DOMAIN? On Wed, 2002-10-02 at 11:54, [EMAIL PROTECTED] wrote: > In August we started having windows domain controller issues. Could it be > the number of users that are running ClearCase at a given point in time? > We have between 40 - 70 users accessing the VOBs at any given time. The > samba config file is setup not run security = SERVER. > > The error logs: > [2002/10/02 10:38:15, 2] passdb/pdb_smbpasswd.c:(170) > startsmbfilepwent_internal: unable to open file > /usr/local/samba/private/smbpa > sswd. Error was No such file or directory > [2002/10/02 10:38:15, 0] passdb/pdb_smbpasswd.c:(1367) > unable to open passdb database. > [2002/10/02 10:38:15, 1] smbd/password.c:(555) > Couldn't find user 'rm38144' in passdb. > [2002/10/02 10:38:15, 2] smbd/reply.c:(962) > NT Password did not match for user 'rm38144'! > [2002/10/02 10:38:15, 1] smbd/reply.c:(998) > Rejecting user 'rm38144': bad password > [2002/10/02 10:38:15, 3] smbd/error.c:(91) > error string = No such file or directory > [2002/10/02 10:38:15, 3] smbd/error.c:(103) > error packet at smbd/reply.c(1000) cmd=115 (SMBsesssetupX) > NT_STATUS_LOGON_FAI > LURE > [2002/10/02 10:38:15, 3] smbd/process.c:(860) > Transaction 397 of length 74 > > I see that the NT Password did not match for user rm38144, however the NT > password and the UNIX password are the same. Could this be something with > the clearcase_albd account? > the interesting part of the transactionis higher in the log i think security=SERVER is tried first then falls through to smbpasswd if there is some problem. all I'm seeing is the part after falling through to smbpasswd (which does not exist in your case) brad -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
