We've noticed this behaviour when Win95 crashes and the next person tries
to logon (we are using roving profiles, samba 1.9.18p10):
- user logs in to win95
- user crashes client
- boot client
- user tries to logon, but it takes *forever* and eventually returns
a "the domain password you suppiled is not correct, or access to your
logon server has been denied" error
- user tries to logon, but it takes *forever* and eventually returns
a the domain password you suppiled is not correct, or access to your
logon server has been denied" error (for a second time)
- user tries to logon and is succesful
- on the server, the smbd process related to the first logon is *still*
running
This problem is reproduceable.
I have set the deadtime parameter to 5 minutes, but I don't think it's
really taking affect because the client is still using the shares...
Anyone have a suggestion here?
Rob Naccarato "Civilized men are more discourteous than savages
Sys Admin because they know they can be impolite without
Sheridan College having their skulls split, as a general thing."
Oakville, Ont. Canada - Robert E. Howard
