Group: Forum Members
Last Login: 12/14/2017 12:40:49 PM
|We are seeing the following in our event logs on DC's. We can see the user (who does not exist).
Trying to figure out how to resolve this happening and determine if it is an issue or hacking attempt.
SourceName=Microsoft Windows security auditing.
Message=An account failed to log on.
Security ID: S-1-0-0
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: S-1-0-0
Account Name: admin
Account Domain: DC2K1203
Failure Reason: Unknown user name or bad password.
Sub Status: 0xC0000064
Caller Process ID: 0x0
Caller Process Name: -
Workstation Name: -
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
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.
host = SuperCharger
source = WinEventLog:ForwardedEvents
sourcetype = WinEventLog:ForwardedEvents
Last Login: 11/14/2013 3:17:47 PM
|It is impossible to say if this is something to worry about based on this event alone. You will have to look at contextual information to determine whether this is malicious in nature. I would look into the quantity of events that are generated, the times they are generated, processes that are running around that time, other users that login before or after the event, and whether this event shows up on other workstations to see if this can provide a clue into whether this is legitimate or not.