Process Monitor (procmon) does not show some UDP / TCP network activity events, shown in Network Monitor

7,927

Solution 1

System is deactivated by the default filter (exclude system events). Delete the filter and these events will show up.

Solution 2

Shot in the dark: Use psexec to run Process Monitor as localsystem.

Share:
7,927

Related videos on Youtube

marsh-wiggle
Author by

marsh-wiggle

Updated on September 18, 2022

Comments

  • marsh-wiggle
    marsh-wiggle almost 2 years

    I observe sometimes a difference between Process Monitor and Network Monitor. Process Monitor does not show some UDP / TCP network events.

    Here is an example:

    net use * \\test12345.domain.local\test

    shows in Netmon as:

    Enter image description here

    shows in Process Monitor:

    Enter image description here

    Why is the NetBIOS nameservice (:137) communication is missing in Process Monitor?

    (I've tested it on several virtual and physical Windows PCs, like Windows Server 2008 R2, Windows 7, and Windows Server 2008.)

    • Justin Dearing
      Justin Dearing over 9 years
      I would ask on the sysinternals forum and for more clues, there is a fork of Wireshark that associates packets with process, if netmon doesn't. It might be that the 137 network traffic happens at the kernel level from a Localsystem level access.
  • Peter Mortensen
    Peter Mortensen over 5 years
    What is "localsystem"? A Windows user account? Or something else? Can you add a reference?