Please Read: Significant Update Planned, Migrating Forum Software This Month

See more
See less

Excessive(?) Security log entries

  • Filter
  • Time
  • Show
Clear All
new posts

  • Excessive(?) Security log entries

    Good Afternoon All!
    I am building a new Windows Server 2008R2 based AD Domain. We have 2 X Domain Controllers and 2 X Member Servers all working very well. One thing however is slightly fixing me and my team. Firstly let me give a little more detail.

    The Servers are named 40, 41, 42 and 43. There are prefixes to these numbers but to stop me having to bother with typing them out each time I'll just stick with the numbers The DC's are 40 and 41 and the FSMO roles are placed as follows :

    040 holds :

    041 holds :

    The site replication links are set at 15 minutes and the cost 100 as standard. The Security log on server is adding Logon and Logoff (plus privileges assignment messages) at quite an alarming rate. I may be worrying about nothing, but it seems like a lot of activity for a domain that isn't servicing any users even. I've copied and pasted an example of one of the LOGON messages as an example and would love to hear from anyone who can decipher what is going on. I can post more message details if needs be..............

    Here it is :

    Log Name: Security
    Source: Microsoft-Windows-Security-Auditing
    Date: 19/07/2012 14:42:10
    Event ID: 4624
    Task Category: Logon
    Level: Information
    Keywords: Audit Success
    User: N/A
    An account was successfully logged on.

    Security ID: NULL SID
    Account Name: -
    Account Domain: -
    Logon ID: 0x0

    Logon Type: 3

    New Logon:
    Security ID: SYSTEM
    Account Name: HQWNVAD040$
    Account Domain: RSPCANET
    Logon ID: 0x1c02c743
    Logon GUID: {2f5e373b-145d-4722-44cd-86882f054fcf}

    Process Information:
    Process ID: 0x0
    Process Name: -

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

    Detailed Authentication Information:
    Logon Process: Kerberos
    Authentication Package: Kerberos
    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="">
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <TimeCreated SystemTime="2012-07-19T13:42:10.847781200Z" />
    <Correlation />
    <Execution ProcessID="500" ThreadID="5996" />
    <Security />
    <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-18</Data>
    <Data Name="TargetUserName">HQWNVAD040$</Data>
    <Data Name="TargetDomainName">RSPCANET</Data>
    <Data Name="TargetLogonId">0x1c02c743</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">Kerberos</Data>
    <Data Name="AuthenticationPackageName">Kerberos</Data>
    <Data Name="WorkstationName">
    <Data Name="LogonGuid">{2F5E373B-145D-4722-44CD-86882F054FCF}</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress"></Data>
    <Data Name="IpPort">59228</Data>

    Thanks everyone!


  • #2
    Re: Excessive(?) Security log entries

    Any printers (maybe IIS or other software) installed on the DCs?

    Type 3 is network logon and the indication is that it is from the local machine account so are there any other logs that you can see?

    Please read this before you post:

    Quis custodiet ipsos custodes?


    • #3
      Re: Excessive(?) Security log entries

      Thanks for your reply Andy. No there are no printers installed or IIS Services configured or running. There are loads of other Log items, it looks like the server logging into the directory, then assigning privileges then logging off and it's doing it for 2 Servers. It's a quite confusing situation and I don't think that there is anything specifically wrong, just need more of an insight..........

      I've got some budget for consultancy in my project so it may make more sense to physically get someone in to take a look.

      Thanks for your input in the meantime...........



      • #4
        Re: Excessive(?) Security log entries

        I've checked ours here and see the 4634 and 4624 events the same as yours. I don't know what is actually happening specifically but the rate isn't what I would call alarming.

        If you have some budget why not get an MS case? Not sure how much they are but their guys are excellent.
        If you find out what it is please let us know.

        Please read this before you post:

        Quis custodiet ipsos custodes?


        • #5
          Re: Excessive(?) Security log entries

          Cheers Andy, that's something that I will certainly consider. I have a few 's to play with in my budget and I'll certainly report back in this thread...........

          Thanks all!