Hi! We recently needed to change all admin passwords when I co worker left the company. Since then, the security logs are filling up with audit failures such as below:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 3/25/2013 11:34:13 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: hcdc1.mydomain.ad
Description:
An account failed to log on.
Subject:
Security ID:
SYSTEM
Account Name:
HCDC1$
Account Domain:
mydomain
Logon ID:
0x3e7
Logon Type:
3
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
Administrator
Account Domain:
mydomain
Failure Information:
Failure Reason:
Unknown user name or bad password.
Status:
0xc000006d
Sub Status:
0xc000006a
Process Information:
Caller Process ID:
0x214
Caller Process Name:
C:\Windows\System32\lsass.exe
Network Information:
Workstation Name:
HCDC1
Source Network Address:
10.1xx.xx.xx
Source Port:
55074
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.
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="2013-03-25T15:34:13.202353900Z" />
<EventRecordID>33047753</EventRecordID>
<Correlation />
<Execution ProcessID="532" ThreadID="1284" />
<Channel>Security</Channel>
<Computer>hcdc1.mydomain.ad</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">HCDC1$</Data>
<Data Name="SubjectDomainName">mydomain</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">Administrator</Data>
<Data Name="TargetDomainName">mydomain</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc000006a</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">Advapi </Data>
<Data Name="AuthenticationPackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
<Data Name="WorkstationName">HCDC1</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x214</Data>
<Data Name="ProcessName">C:\Windows\System32\lsass.exe</Data>
<Data Name="IpAddress">10.108.192.170</Data>
<Data Name="IpPort">55074</Data>
</EventData>
</Event>