none
Constant user lockouts due to ADVAPI / lsass.exe RRS feed

  • Question

  • We have 2 developers who are constantly being locked out for failed logon attempts from something running in the background.  The event viewer for both users show the same error and any help figuring out how to fix this would be greatly appreciated.  

    One thing to mention is that the source network address listed (10.20.1.1) is the IP for our Cyblock web filtering appliance in case that helps.  Thanks in advance, details below:

    An account failed to log on.

    Subject:
    Security ID: SYSTEM
    Account Name: DC001$
    Account Domain: PRESSLER
    Logon ID: 0x3e7

    Logon Type: 3

    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name: *******
    Account Domain: *******

    Failure Information:
    Failure Reason: Unknown user name or bad password.
    Status: 0xc000006d
    Sub Status: 0xc000006a

    Process Information:
    Caller Process ID: 0x20c
    Caller Process Name: C:\Windows\System32\lsass.exe

    Network Information:
    Workstation Name: DC001
    Source Network Address: 10.x.x.x
    Source Port: 35547

    Detailed Authentication Information:
    Logon Process: Advapi  
    Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    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.




    • Edited by skitzes Wednesday, September 30, 2015 7:48 PM
    Wednesday, September 30, 2015 3:47 PM

Answers

All replies

  • Hi skitzes,

    Thanks for your post.

    You can logon several DC to check more events to narrow down the cause of this issue. You can also check the user’s name to narrow down the computer.

    You can use the following tools to troubleshoot this issue.

    Account Lockout and Management Tools
    http://www.microsoft.com/en-us/download/details.aspx?id=18465

    How to use the EventCombMT utility to search event logs for account lockouts
    https://support.microsoft.com/en-us/kb/824209

    Besides, the common causes for account lock outs are: Saved Browser Passwords, User Account used for running specific services, Saved Passwords on Network Printers, Cached passwords on Terminal Server sessions etc.

    Please refer to the thread discussed before for more details.

    User's account keeps getting locked out, but why?

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/84acda4e-8fa9-4d56-837c-127c0bf463ff/users-account-keeps-getting-locked-out-but-why?forum=winservergen

    Best Regards,

    Mary Dong


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

    Thursday, October 1, 2015 11:11 AM
    Moderator
  • Hello,

    Were you able to resolve this? If so, what was the solution?

    Thanks in advance.

    Monday, March 28, 2016 2:29 PM
  • There are passwords that can be stored in the SYSTEM context that can't be seen in the normal Credential Manager view.<o:p></o:p>

    Download PsExec.exe from Technet and copy it to C:\Windows\System32 .<o:p></o:p>

    From a command prompt run:    psexec -i -s -d cmd.exe<o:p></o:p>

    From the new DOS window run:  rundll32 keymgr.dll,KRShowKeyMgr<o:p></o:p>

    Remove any items that appear in the list of Stored User Names and Passwords.  Restart the computer<o:p></o:p>

    Monday, September 9, 2019 7:23 PM