[Samba] XP Pro, Samba-3 authentication consistancy problems

[Damian Gerow]

I really don't know where to start on this one...

We have an XP Pro workstation.  The user on this workstation is, say, 'bob'.
Earlier this year, bob would log in to his workstation with a different
password than was on the Samba machine.  I /think/ that's what's causing the
problems, but I'm not sure.

Anyhow, we had specifically mapped drives on bob's workstation using his
samba password.  Lately, bob's been having troubles where he can mount
drives but can't see the contents.  In fact, trying to view the contents can
crash his entire computer -- we have to end the explorer task, and re-start
it.

So we changed passwords everywhere to be the new password, killed all drive
mappings, and tried again.  The weird thing is, we'd be able to list the
contents of the share for a couple of minutes, then we'd lose it again.  The
samba logs actually showed something like this:

    [2003/06/24 09:57:12, 2] auth/auth.c:check_ntlm_password(288)
      check_ntlm_password:  authentication for user [bob] -> [bob] -> [bob] suceeded
    [2003/06/24 09:58:47, 2] smbd/server.c:exit_server(558)
      Closing connections
    [2003/06/24 09:59:35, 2] auth/auth.c:check_ntlm_password(295)
      check_ntlm_password:  Authentication for user [bob] -> [bob] FAILED with error NT_STATUS_WRONG_PASSWORD
    [2003/06/24 09:59:35, 2] smbd/server.c:exit_server(558)
      Closing connections
    [2003/06/24 09:59:35, 2] auth/auth.c:check_ntlm_password(295)
      check_ntlm_password:  Authentication for user [bob] -> [bob] FAILED with error NT_STATUS_WRONG_PASSWORD

It looks almost like the workstation is trying a /different/ password the
second time.

So, we re-mapped all the drives, explicitly specifying the password.  Then
tried it all again using the /old/ password on both machines.  At this
specific moment, bob has access to our samba server, but it's hard to say
for how long.

I realize this is all a bit erratic, but I haven't been able to find a
common ground amongst all this.  I'm willing to just blame the workstation,
just wondering if anyone can give any pointers/eye openers before I do?