Active Directory user account is not locked according to bad password attempt event logs.

Md. Mahfuzur Rahman 346 Reputation points
2022-08-21T12:10:18.12+00:00

we are getting 4771 event log in security log for Bad password attempt but user did not lock. According to our password policy user should lock 3 invalid password within 5 mins. but we have checked event log we found bad password attempt. if we checked manually by bad password, user lockout policy is working. user is locked after 3 times bad password attempt. but we are getting huge bad password attempt in event log but user did not lock. screen shot is given below- ![233205-image.png][1] [1]: /api/attachments/233205-image.png?platform=QnA

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,843 questions
0 comments No comments
{count} votes

Accepted answer
  1. JimmySalian-2011 41,916 Reputation points
    2022-08-21T18:16:02.833+00:00

    Hi,

    Thank you for asking this question on the Microsoft Q&A Platform.

    As per the logs it is 0X18 and preauthentication failed so I guess you will have to check the event logs on the device and see if there is any services or tasks running that is causing the lockouts? Also can you check the pwdHistoryLength is at least 2, an authentication attempt with the previous password in password history will not increment the badPwdCount, and so will not cause a lockout.

    Details of the event ID - event.aspx

    Check this and verify the settings please 32490.active-directory-bad-passwords-and-account-lockout.aspx

    ==
    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


2 additional answers

Sort by: Most helpful
  1. Gary Reynolds 9,391 Reputation points
    2022-08-21T19:51:33.147+00:00

    Hi,

    Do all the events shown in the screenshot relate to the same user?

    A bit of background on the account lock out process. Each domain controller keeps its own count of the number of failed logon attempts per user, so if a user authenticates against a different DCs, they could exceed the maximum failed attempts defined in the password policy, to ensure that the password policy is enforced the follow mechanism is used.

    When a domain user provides a bad password, the authenticating domain controller will increment it's own copy of the bad password count for that user, if this exceeds the policy the DC will lock the account. If not, it will then send the authentication request to the PDC to confirm the password, in case the password has recently been changed. This means that the PDC will see all failed authentication attempts.

    If the bad password count for a user, on any DC exceed the policy then the account locked, and AD replicates this to the other DCs in the domain. In a multi-DC domain, the PDC is usually the DC that locks a user's account.

    You can use the post below to check the number of bad passwords (bad pwd column) that have been received on each domain controller and if the PDC bad password count is also incrementing with each failed logon, in case the failed logons are not being sent to the PDC or the locked status is not being replicated to the other DCs.

    https://nettools.net/troubleshoot-account-lockouts/

    Gary.


  2. Limitless Technology 39,351 Reputation points
    2022-08-22T14:43:12.663+00:00

    Hello,

    The failure code 0x18 references to the bad password attempt & there can be many reasons like attack bcoz of worm/viruses, password attack. You need to verify, from where the attempt is coming from using netmon or wireshark tool. There is no easy way to find out the reason for invalid (0x18)password attempt coming from w/o analyzing the traffic.

    Reference for more details: https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4771

    -----------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments