none
Account getting locked every day, 5 bad password attempts

    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:39 AM

All replies

  • HI gabrielf3003,

     

    First of all, I notice that this following link is also your thread.

    https://social.technet.microsoft.com/Forums/windows/en-US/30cdab60-fdaf-403e-a399-c06392989f73/account-getting-locked-every-day-5-bad-password-attempts?forum=winserversecurity

     

    Based on your description, it is a domain account which is locked, right?

    The message “Package Name (NTLM only):” indicates this logon process is called by a local account. It should be Kerberos if it is a domain account which is trying to logon.

    https://technet.microsoft.com/en-us/library/cc780332(v=ws.10).aspx

    The message “Security ID: NULL SID “indicates the account could be corrupted already.

     

    Since this issues still persists in new machine, it is suggested to create a new account for him if you have the domain administrator permission.

     

    Best regards.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, March 18, 2016 10:22 AM
    Moderator
  • Can the user (Konrad Jablonski?) log on successfully and work as usual? If so, will he be logged out if a logon attempt is being made?


    Best regards George

    Monday, March 21, 2016 11:56 AM
  • Thanks Ricki for the Suggestion, we are trying to avoid the account recreation, but if we don't find anything else, that's going to probably be next step, Appreciate the advice.
    Monday, March 21, 2016 2:10 PM
  • Hi George, yes the user can successfully login to the account with no problems, and he will not be kicked out from the account when an incorrect attempt happened, he will know when the account is locked out because the network resources will be limited for him.
    Monday, March 21, 2016 2:12 PM
  • I'm puzzled that this happens even if the computer is off. "localhost" must then be somewhere else. Is he logged on to multiple computers? Maybe some forgotten one somewhere. Log out Konrad, shut down his computer and do an AD search for all logged in users and computers.


    Best regards George


    Monday, March 21, 2016 2:20 PM
  • hey gabrielf3003,

    did you already attempt to check Event ID 4740 on Domain Controller Security logs? if theres any  machine on the network using some old password etc, it will keep locking his account. 4740 can give details of that machine. 

    If not already attempted, you can check this blog: 

    https://blogs.technet.microsoft.com/heyscriptingguy/2012/12/27/use-powershell-to-find-the-location-of-a-locked-out-user/

    Monday, March 21, 2016 2:28 PM
  • We have removed all the other computers that were on the domain under his name, they were wiped out and kicked out from the Domain. It is a really weird case.

    Monday, March 21, 2016 4:03 PM
  • With all respect Gabriel, but no way a computer that is shut down can issue a login request. You are missing something!

    Best regards George

    Monday, March 21, 2016 4:08 PM
  • I remember a similar case, the user was on vacation, yet he was logged on. A coworker used his credentials. Easy to check with Active Directory Users and Computers. Do that!


    Best regards George

    Monday, March 21, 2016 4:11 PM