Thousands of Logon Logoff events


  • For one of my user, i see around 10,000 events every 5 minutes.  90% is logon and logoff with w3wp.exe but they do not show IP address.  User have Outlook, multiple ActiveSync devices, and MDM app for some devices.  I've turned each device off and check number of events associated with his username but still can't isolate.

    Any idea how to trace this out to find the source?


    An account was successfully logged on.

    Security ID: SYSTEM
    Account Name: CASSERVER$
    Account Domain: DOMAIN
    Logon ID: 0x3e7

    Logon Type: 3

    New Logon:
    Security ID: DOMAIN\user1
    Account Name: user1
    Account Domain: CANYON
    Logon ID: 0xxxxxxxxx3
    Logon GUID: {xxxxxd36-xxx8-d318-5b11-42cdfeexxxxx}

    Process Information:
    Process ID: 0xbcc
    Process Name: C:\Windows\System32\inetsrv\w3wp.exe

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

    Detailed Authentication Information:
    Logon Process: Authz   
    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.

    Wednesday, May 09, 2018 9:37 PM

All replies

  • The IIS logs would show the IP address.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thursday, May 10, 2018 2:15 AM
  • Agree with Ed, we can analyze IIS log (C:\inetpub\logs\LogFiles\W3SVC1) to find the client information, including client IP, protocol, account information.
    How to analyse IIS logs using LogParser / LogParser Studio

    Then, we can contact this effect account, double check the configuration on client and find out the reason of this problem.

    Best Regards,
    Allen Wang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, May 11, 2018 2:23 AM