#Endless online private server 2015 code#

Call Microsoft Support for the code fix, which updates nine core OS components. This problem exists on all Win2K systems, from the original release through Service Pack 2 (SP2). If that user doesn't enter the correct password the first time, the authenticating DC will lock the account again. If the user subsequently logs on to the same DC where the account lockout occurred, the DC will still have the account’s bad password count because the replicating DC didn't replicate the new value.

When the DC on which you unlocked the account next replicates, it correctly replicates the account's unlocked status, but it doesn't replicate new bad password count (0). 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.