Network Monitor 3.4 - no network adapters bound to the netmon driver

Answered Network Monitor 3.4 - no network adapters bound to the netmon driver

  • Thursday, September 01, 2011 1:23 PM
     
     

    Hello

    I test installed NM3.4 on my laptop (Win7) and it worked great. But now I have installed it on the server where I actually want to use it and the Select Networks pane doesn't show any network adapters. Can anyone suggest a fix?

    The server is Windows 2003 Server x32 SP2. It has two physical network cards which are both bound (only) to HP Network Configuration Utility. They are used as a third "teamed" adapter which has the Network Monitor Driver bound to it, along with IPv4 and all the usual stuff

    The testing I have done is:

    sc query nm -->

      SERVICENAME: nm

      STATE: 4 RUNNING

    net start nm  --> The requested service has already been started

    nmcap /displaynetworks -->

    Network Monitor Command Line Capture 3.4.2350.0

    Where can I go from here?

    Suggestions gratefully received,

    Matt


    _ _ / . _ / _ / _

All Replies

  • Thursday, September 01, 2011 3:33 PM
     
     

    I've thought of something else which may be relevant. The server has a VPN connection to another network. The VPN adapter doesn't show up in either the NM3.4 window, or the Network Connections window. It does show up in Device Manager but only after doing this... http://support.microsoft.com/kb/825826/#Method_6

    Actually the VPN traffic is the traffic that I'm most interested in


    _ _ / . _ / _ / _
  • Wednesday, September 07, 2011 1:55 PM
    Owner
     
     

    There are potention issues captureing on teamed nics, but usually this shows up as seeing only traffic in one directions.  This is usualy due to how the NIC teaming driver is written.

    But I beleive that if the NIC isn't showing up, then you are running into a different problem.  Furthermore, VPN traffic will show up as NDISWAN driver in the list of interfaces.

    If you run Netmon as admin, does this change anything?

    Thanks,

    Paul

  • Wednesday, September 07, 2011 4:24 PM
     
     

    Should have said in the first post because I had read that it can be a factor - situation described above is when running as Administrator...

     


    _ _ / . _ / _ / _
  • Monday, September 12, 2011 1:27 PM
    Owner
     
     Answered

    The only time I've seen this problem is when third party stack drivers are involved. If you look at the NIC properties, what are all the drivers enabled for the NICs?  In particular, any anti-virus or Virtual Machine type software installed?

    Paul

     

  • Tuesday, April 24, 2012 9:11 AM
     
     Proposed Answer
    Execute runas administrator.
    • Proposed As Answer by Jan Bilek Monday, June 25, 2012 8:20 AM
    •