The following has been listen in the logbook viewer in
"home premium". Can someone help me with the type login?

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 2008-04-20 18:45:10
Event ID: 4624
Task Category: login
Level: Information
Keywords: Audit Success
User: N/A
Computer: Lester-PC
Description:
An account was successfully logged on.

Subject:
Security ID: SYSTEM
Account Name: LESTER-PC$
Account Domain: WORKGROUP
login ID: 0x3e7

login Type: 5

New login:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x210
Process Name: C:\Windows\System32\services.exe

Network Information:
Workstation Name:
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
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="2008-04-20T22:45:10.566Z" />
<EventRecordID>2773</EventRecordID>
<Correlation />
<Execution ProcessID="540" ThreadID="2064" />
<Channel>Security</Channel>
<Computer>Lester-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">LESTER-PC$</Data>
<Data Name="SubjectDomainName">WORKGROUP</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="TargetUserSid">S-1-5-18</Data>
<Data Name="TargetUserName">SYSTEM</Data>
<Data Name="TargetDomainName">NT AUTHORITY</Data>
<Data Name="TargetLogonId">0x3e7</Data>
<Data Name="LogonType">5</Data>
<Data Name="LogonProcessName">Advapi </Data>
<Data Name="AuthenticationPackageName">Negotiate</Data>
<Data Name="WorkstationName">
</Data>
<Data
Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x210</Data>
<Data
Name="ProcessName">C:\Windows\System32\services.exe</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>

I have tied my user account to administration for 2
applications that require it. I am sure it's a deadly combo.

Note: I also recieve security note that windows firewall
has blocked an application from receiving incoming
communications, but could not inform me. Can someone inform
me what this could mean?
--
Visit Family Radio Today
http://www.familyradio.com/

Logon type 5 is a Service logon. You can find the logon types here:
http://msdn2.microsoft.com/en-us/library/aa380129.aspx. This is a service
that runs as Local System.

I don't know what you mean by "tied my user account..." Can you elaborate?

The notice from Windows Firewall is because some application tried to listen
on the network. Windows Firewall blocked that and is informing you of that
fact. It should say in the message which application it is that is trying to
listen.
---
Your question may already be answered in Windows Vista Security:
http://www.amazon.com/gp/product/047...otectyourwi-20


"Lester Stiefel" wrote:

> The following has been listen in the logbook viewer in
> "home premium". Can someone help me with the type login?
>
> Log Name: Security
> Source: Microsoft-Windows-Security-Auditing
> Date: 2008-04-20 18:45:10
> Event ID: 4624
> Task Category: login
> Level: Information
> Keywords: Audit Success
> User: N/A
> Computer: Lester-PC
> Description:
> An account was successfully logged on.
>
> Subject:
> Security ID: SYSTEM
> Account Name: LESTER-PC$
> Account Domain: WORKGROUP
> login ID: 0x3e7
>
> login Type: 5
>
> New login:
> Security ID: SYSTEM
> Account Name: SYSTEM
> Account Domain: NT AUTHORITY
> Logon ID: 0x3e7
> Logon GUID: {00000000-0000-0000-0000-000000000000}
>
> Process Information:
> Process ID: 0x210
> Process Name: C:\Windows\System32\services.exe
>
> Network Information:
> Workstation Name:
> Source Network Address: -
> Source Port: -
>
> Detailed Authentication Information:
> Logon Process: Advapi
> Authentication Package: Negotiate
> Transited Services: -
> Package Name (NTLM only): -
> 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="2008-04-20T22:45:10.566Z" />
> <EventRecordID>2773</EventRecordID>
> <Correlation />
> <Execution ProcessID="540" ThreadID="2064" />
> <Channel>Security</Channel>
> <Computer>Lester-PC</Computer>
> <Security />
> </System>
> <EventData>
> <Data Name="SubjectUserSid">S-1-5-18</Data>
> <Data Name="SubjectUserName">LESTER-PC$</Data>
> <Data Name="SubjectDomainName">WORKGROUP</Data>
> <Data Name="SubjectLogonId">0x3e7</Data>
> <Data Name="TargetUserSid">S-1-5-18</Data>
> <Data Name="TargetUserName">SYSTEM</Data>
> <Data Name="TargetDomainName">NT AUTHORITY</Data>
> <Data Name="TargetLogonId">0x3e7</Data>
> <Data Name="LogonType">5</Data>
> <Data Name="LogonProcessName">Advapi </Data>
> <Data Name="AuthenticationPackageName">Negotiate</Data>
> <Data Name="WorkstationName">
> </Data>
> <Data
> Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
> <Data Name="TransmittedServices">-</Data>
> <Data Name="LmPackageName">-</Data>
> <Data Name="KeyLength">0</Data>
> <Data Name="ProcessId">0x210</Data>
> <Data
> Name="ProcessName">C:\Windows\System32\services.exe</Data>
> <Data Name="IpAddress">-</Data>
> <Data Name="IpPort">-</Data>
> </EventData>
> </Event>
>
> I have tied my user account to administration for 2
> applications that require it. I am sure it's a deadly combo.
>
> Note: I also recieve security note that windows firewall
> has blocked an application from receiving incoming
> communications, but could not inform me. Can someone inform
> me what this could mean?
> --
> Visit Family Radio Today
> http://www.familyradio.com/
>