samba rejection error on log level 1 with win xp pc reboots

[p7]

hi all,

we have a samba PDC on an hpux box with 400 users logging in. all is well. i noticed in the samba logs (log level 1) that whenever a user reboots his pc (every day) the first time it automatically tries to map to the samba server it gets a reject. then when the user opens up his app it goes right in. the users arent even aware of this. if they disconnect n remap, i dont see this error in the samba log, only when they reboot.
anyone ever seen this? thx in advance.

example:

[2006/04/19 07:01:33, 1] smbd/reply.c:(1037)
Rejecting user 'keaceve': authentication failed
[2006/04/19 07:01:40, 1] smbd/service.c:(636)
ar5046 (10.12.12.111) connect to service metashrd as user keaceve (uid=847, gi
d=104) (pid 23430)

[Steven E. Protter · Accepted solution]

Shalom,

Probably the windows user has a remembered password that is no longer valid.

Its probably a user education issue. Samba appears to be functioning normally.

Confirm the user login with the user and you should be able to assist him/her in correcting the windows configuration.

SEP

[p7]

hi

the wierd thing is, its happening to all the users and its an automatic mapping once the pc reboots. really no user intervention is required. must be something the way win xp send/stores passwds on bootup?

[eric roseme]

Hi Pasquale,

I saw your post to samba.org for this question (with no replies).

Bump your log level up to 5 and dupe the scenario, then post your log.client here along with your smb.conf. You can bump your log level with smbcontrol (for CIFS, it's /opt/samba/bin/smbcontrol, for Samba, it's /usr/local/samba/bin/smbcontrol) "smbcontrol smbd debug 10"

In your ITRC topic a couple of weeks ago you asked for some logging advice. I replied to not send all logs to log.smbd. Make sure that you use %m in your log file config and post the log.client for just that connection that you are duplicating.

BTW - Windows does all kinds of crazy things during auth-n and session startup. If you literally have a "Samba PDC", then you are using "securtity = user", which means no Kerberos, which simplifies things a lot. One scenario that I have seen is that the prior connection does not close fast enough to be finished before the next auth-n attempt from the same user - and thus gets rejected. But without more log data, it difficult to know.

Also post your CIFS/Samba version, HP-UX version, Windows client version.

Eric Roseme

[p7]

thx all for ur advice