I had
instances where a User:
wasn't
using a password protected screen saver and waiting on a mainframe job to
complete just running a terminal emulator
I have
had Users get their new PC, automatically get prompted to change their password
because Support Staff had to log in with the User's ID to setup the PC and
immediately after the password change the account locked. Some suggest that the
account locked because the domain password and the locally cached password used
for the screen saver password were out of sync but I don't buy that. I would
happen every time.
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm-----Original Message-----
From: Martin Blackstone [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 2:44 PM
To: NT System Admin Issues
Subject: RE: Win2K Pro client / NT domain Account LockoutsAre you SURE it isn't user error?http://www.sunbelt-software.com/ntsysadmin_list_charter.htm-----Original Message-----
From: Heavner, Charlie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 11:31 AM
To: NT System Admin Issues
Subject: Win2K Pro client / NT domain Account LockoutsI'm deploying Win2K Pro in a Mixed environment (WinNT domain).Randomly, Win2K Pro clients will experience an Account Lockout.I think that it is an NTLMv2 replication problem across DCs but don't have a good handle on how to prove it.Anybody ever experience this and how did you resolve it?I've not changed any of the default security settings in the LGPO on my clients.We aren't running any Win2K servers yet.Thanks for any help,Charliehttp://www.sunbelt-software.com/ntsysadmin_list_charter.htm
