Request for Help.

[Neil.Meadows at itservices.co.uk]

Neil Meadows at ITS
15/01/2001 14:08

Dear all,

Has anybody any idea about this ?

Samba version 2.0.4b
NT Client Version 4 (Service Pack 6)
Solaris version 5.6
NT password server-NT Server V4 (Service Pack 5)

One of our applications requires up to three Samba shares to be mapped to the NT
desktop before being able to access their data files (Both the data files and
Samba are installed on Unix server A). This is done automatically when they
login to NT. Depending on  their level of security, users will be mapped to
either:-

Share A
Share A+B

Share A and B require specific Unix logons and in the case of B, membership of a
group G.

Password verification is done by an NT password server.

Intermittently some users (others may be OK) who use share A and/or B are thrown
out of the application on login with the message:-

"\\[servername]\[share A]\support\crldm3.all does not exist"

The error message in the users samba log file is as follows:-

[2001/01/10 13:34:17, 1] smbd/password.c:(1131)
  password server [SERVER NAME]  rejected the password
[2001/01/10 13:34:17, 1] smbd/password.c:(504)
  Couldn't find user 'mjp7' in smb_passwd file.
[2001/01/10 13:34:17, 2] smbd/reply.c:(830)
  NT Password did not match for user 'mjp7' ! Defaulting to Lanman
[2001/01/10 13:34:17, 1] smbd/password.c:(504)
  Couldn't find user 'mjp7' in smb_passwd file.
[2001/01/10 13:34:17, 3] smbd/error.c:(138)
  error packet at line 840 cmd=115 (SMBsesssetupX) eclass=2 ecode=2
[2001/01/10 13:34:28, 3] smbd/process.c:(615)
  Transaction 4 of length 197
[2001/01/10 13:34:28, 3] smbd/process.c:(448)
  switch message SMBsesssetupX (pid 4402)
[2001/01/10 13:34:28, 3] smbd/reply.c:(721)
  Domain=[DOMAIN NAME]  NativeOS=[Windows NT 1381] NativeLanMan=[]
[2001/01/10 13:34:28, 3] smbd/reply.c:(725)
  sesssetupX:name=[mjp7]

This can be repeated a number of times in the log.

The only way back in to the application is to log off NT and go back in. The
users NT account may then be locked,
the above may repeat itself or the user may get back into the application
successfully.

Any suggestions gratefully received.

Neil.