Doing so resets the bad password count to 0 and unlocks the user account.
You can log on as an Administrator and unlock the user account from a different DC (i.e., not the one that originally locked the user account). Unfortunately, when the authenticating DC replicates, it replicates the account’s bad password count and its locked status. When a user enters the maximum number of bad passwords (e.g., three), the authenticating DC records the number of bad passwords and then locks the user account. However, Windows 2000's domain controller (DC) replication code contains a bug that produces unexpected results when the system locks down a user account after a user enters the maximum number of bad passwords. Network administrators usually set an account lockout policy to discourage malicious users from trying to hack account passwords.
0 kommentar(er)
