On looking at my logs, I see several entires like this...
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 12/10/2012 3:41:56 PM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: 2k8d-194-121
Description:
An account was successfully logged on.
Subject:
Security ID:
NULL SID
Account Name:
-
Account Domain:-
Logon ID:
0x0
Logon Type:3
New Logon:
Security ID:
ANONYMOUS LOGON
Account Name:
ANONYMOUS LOGON
Account Domain:NT AUTHORITY
Logon ID:
0xc2aef4ba
Logon GUID:
{00000000-0000-0000-0000-000000000000}
Process Information:
Process ID:
0x0
Process Name:
-
Network Information:
Workstation Name:SRVTSIOSHOPPING
Source Network Address:186.210.60.41
Source Port:
1647
Detailed Authentication Information:
Logon Process:NtLmSsp
Authentication Package:NTLM
Transited Services:-
Package Name (NTLM only):NTLM V1
Key Length:
0
This event is generated when a logon session is created. It is generated on the computer that was accessed.
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 occurred. The most common types are 2 (interactive) and 3 (network).
The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
The network 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.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- 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>4624</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2012-12-10T23:41:56.378Z" />
<EventRecordID>1042594</EventRecordID>
<Correlation />
<Execution ProcessID="676" ThreadID="780" />
<Channel>Security</Channel>
<Computer>2k8d-194-121</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-5-7</Data>
<Data Name="TargetUserName">ANONYMOUS LOGON</Data>
<Data Name="TargetDomainName">NT AUTHORITY</Data>
<Data Name="TargetLogonId">0xc2aef4ba</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">SRVTSIOSHOPPING</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">NTLM V1</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">186.210.60.41</Data>
<Data Name="IpPort">1647</Data>
</EventData>
</Event>
The IP Address is usually different, but I see a lot of them. How is someone able to log in when I have only 1 user account active, it uses a non standard name, and everywhere I look, it doesn't look like any kind of anonymous login is enable(mainly checked GPEdit.msc, but may be looking at the wrong things I guess?).