troubleshooting Question

Server generating lots of 4625 logon failure event log entries

Avatar of OzoneFriendly
OzoneFriendly asked on
SecurityWindows Server 2012
5 Comments2 Solutions2756 ViewsLast Modified:
I am looking at a Windows Server 2012 Essentials that is generating one of these event log entries repeatedly, sometimes multiple times a second, sometimes every 5 minutes. There are over 230,000 of them in the log right now.

I've been googling like a madman but have not been able to find out more information about how to track back what exactly is doing this, it appears to be something on the server itself.

Any advice on how to narrow this down would be greatly appreciated.

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          27/03/2017 12:26:03 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      {NameOfTheServer}.{NameOfTheDomain}.local
Description:
An account failed to log on.

Subject:
      Security ID:            SYSTEM
      Account Name:            {NameOfTheServer}$
      Account Domain:            {NameOfTheDomain}
      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:            0xC0000064

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

Network Information:
      Workstation Name:      {NameOfTheServer}
      Source Network Address:      -
      Source Port:            -

Detailed Authentication Information:
      Logon Process:            Schannel
      Authentication Package:      Kerberos
      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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2017-03-27T02:26:03.902624800Z" />
    <EventRecordID>44567885</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="31404" />
    <Channel>Security</Channel>
    <Computer>{NameOfTheServer}.{NameOfTheDomain}.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">{NameOfTheServer}$</Data>
    <Data Name="SubjectDomainName">{NameOfTheDomain}</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">
    </Data>
    <Data Name="TargetDomainName">
    </Data>
    <Data Name="Status">0xc000006d</Data>
    <Data Name="FailureReason">%%2313</Data>
    <Data Name="SubStatus">0xc0000064</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">Schannel</Data>
    <Data Name="AuthenticationPackageName">Kerberos</Data>
    <Data Name="WorkstationName">{NameOfTheServer}</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x264</Data>
    <Data Name="ProcessName">C:\Windows\System32\lsass.exe</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
  </EventData>
</Event>
ASKER CERTIFIED SOLUTION
E A
Tech Lead

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 2 Answers and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros