howard ambler

All,

Has anyone else experience this:

Win2K SP3 native running as child domain. 3 sites set up on different
subnets. Replication is set to the lowest time unit (15 mins). Accounts
lockout after 20 incorrect passwords.

When a user changes password it will continually lock them out (account
lockout) for a couple of days until the weekend and then when they come in
on Monday all will be well (usually).

Can anyone explain this as all MS articles on bad password count and lockout
say that these problems were fixed in SP3.

With Thanks


Howard Ambler (MCSE, CCNA)

mike ford

sounds like the user is logged into more than one
computer, changes password on one, and is locked out by
the other. On Friday the person shutsdown all the
computers and therefore is logged out of the offending
computer.

I would check the DC Security logs and find out from which
computer the lock out is originating. Keep in mind if you
have multiple DC you will have to check all of there logs.

on different

mins). Accounts

them out (account

when they come in

password count and lockout