none
Account getting locked every day, 5 bad password attempts RRS feed

  • Question

  • I am facing an issue with a user which is getting his Account locked out every day, we have tried all the possible troubleshooting,

    network drives, drivers, applications, mobile device, etc ,  we even built a new machine and it same is happening. Everyday there are 5 incorrect password attempts. This is happening even if the machine is off.
    The DC is not showing the source, it is just marking it as \\Localhost: , this is happening to random hours, not at the same hours everyday

    on the local machine I found these events:

    An account failed to log on.

    Subject:
    Security ID: SYSTEM
    Account Name: PKC000122436005$
    Account Domain: ADS
    Logon ID: 0x3E7

    Logon Type: 7

    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name: Konrad Jablonski
    Account Domain: ADS

    Failure Information:
    Failure Reason: Account locked out.
    Status: 0xC0000234
    Sub Status: 0x0

    Process Information:
    Caller Process ID: 0x3ae8
    Caller Process Name: C:\Windows\System32\winlogon.exe

    Network Information:
    Workstation Name: PKC000122436005
    Source Network Address: 127.0.0.1
    Source Port: 0

    Detailed Authentication Information:
    Logon Process: User32 
    Authentication Package: Negotiate
    Transited Services: -
    Package Name (NTLM only): -
    Key Length: 0

    This event is generated when a logon request fails. It is generated on the computer where access was attempted.

    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

    The Process Information fields indicate which account and process on the system requested the logon.

    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.




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


    An account failed to log on.

    Subject:
    Security ID: SYSTEM
    Account Name: PKC000122436005$
    Account Domain: ADS
    Logon ID: 0x3E7

    Logon Type: 2

    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name: Konrad Jablonski
    Account Domain: ADS

    Failure Information:
    Failure Reason: Account locked out.
    Status: 0xC0000234
    Sub Status: 0x0

    Process Information:
    Caller Process ID: 0x27dc
    Caller Process Name: C:\Windows\System32\LogonUI.exe

    Network Information:
    Workstation Name: PKC000122436005
    Source Network Address: -
    Source Port: -

    Detailed Authentication Information:
    Logon Process: Advapi  
    Authentication Package: Negotiate
    Transited Services: -
    Package Name (NTLM only): -
    Key Length: 0

    This event is generated when a logon request fails. It is generated on the computer where access was attempted.

    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

    The Process Information fields indicate which account and process on the system requested the logon.

    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

    Please advise.

    Wednesday, March 16, 2016 11:40 AM

All replies

  • Hi gabrielf3003,

    Since you have already checked quite a lot of sources that can have saved credentials, I would suggest you to use Account Lockout Status tool (which can be downloaded from https://www.microsoft.com/en-us/download/details.aspx?id=15201), if you haven't already, to determine the DC which is initiating the lock. From there, investigate the security audit log of that DC. See if any anomalies exist.


    Muditha Jayath Chathuranga | MCSA: Office 365 | Microsoft Specialist: Implementing Microsoft Azure Infrastructure Solutions | http://www.msnix.com | If my answer helped you, kindly propose as answer and/or mark as answer where applicable.

    Thursday, March 17, 2016 11:56 AM