locked
Why can't I see any adapters to select after I just installed Network Monitor? RRS feed

All replies

  • Hi,

    Thanks for posting in the forum.  If you open up the properties for your local area connection (or the network device you're working with) in your Network Connections, do you see the 'Microsoft Network Monitor 3 Driver' checked in the list that says 'This connection uses the following items:'?

    Thanks,


    Michael Hawker | Program Manager | Network Monitor

    Monday, February 27, 2012 10:06 PM
  • Thank you for response. Yes, I do. See screenshot.

    Tuesday, February 28, 2012 5:32 AM
  • There seems to be a bunch of other dirvers installed which might be interfering.  In particular the VMware and Virtualbox drivers are something to be weary of.  There have been reported issues in the past where these drivers interfer with our NDIS filter driver.  I would test with out them installed and see if they change your behavior.

    I was also verify the driver is started by running "sc query nm3" from a command prompt.  It should state the driver is installed and running.

    Paul

    Tuesday, February 28, 2012 3:33 PM
  • I would test with out them installed and see if they change your behavior.

    Thank you. I will test.

    I was also verify the driver is started by running "sc query nm3" from a command prompt.  It should state the driver is installed and running.

    It is running. When I wrote in my initial message

    NM3 is running (and bound to my network card).

    I meant exactly that.

    Tuesday, February 28, 2012 3:54 PM
  • I did some experiments, still without success.

    1. Disabled VMWare, VirtualBox and Kaspersky in the Connection Properties dialog shown above (cleared check boxes).

    2. Disabled the npf driver from the wireshark suite (start=disabled).

    3. Rebooted.

    Result is still the same. Only some isatap adapter is shown in "select network" pane:

    Here is output from ipconfig /all:


    Настройка протокола IP для Windows

       Имя компьютера  . . . . . . . . . : atlas
       Основной DNS-суффикс  . . . . . . :
       Тип узла. . . . . . . . . . . . . : Гибридный
       IP-маршрутизация включена . . . . : Нет
       WINS-прокси включен . . . . . . . : Нет
       Порядок просмотра суффиксов DNS . : rinet.ru

    Ethernet adapter Подключение по локальной сети:

       DNS-суффикс подключения . . . . . : rinet.ru
       Описание. . . . . . . . . . . . . : NVIDIA nForce Networking Controller
       Физический адрес. . . . . . . . . : 00-24-1D-01-D8-08
       DHCP включен. . . . . . . . . . . : Да
       Автонастройка включена. . . . . . : Да
       IPv4-адрес. . . . . . . . . . . . : 192.168.0.2(Основной)
       Маска подсети . . . . . . . . . . : 255.255.255.0
       Аренда получена. . . . . . . . . . : 29 февраля 2012 г. 13:18:52
       Срок аренды истекает. . . . . . . . . . : 7 марта 2012 г. 13:18:51
       Основной шлюз. . . . . . . . . : 192.168.0.1
       DHCP-сервер. . . . . . . . . . . : 192.168.0.1
       DNS-серверы. . . . . . . . . . . : 192.168.0.1
       NetBios через TCP/IP. . . . . . . . : Включен

    Туннельный адаптер Подключение по локальной сети*:

       Состояние носителя. . . . . . . . : Носитель отключен
       DNS-суффикс подключения . . . . . : rinet.ru
       Описание. . . . . . . . . . . . . : isatap.rinet.ru
       Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP включен. . . . . . . . . . . : Нет
       Автонастройка включена. . . . . . : Да

    Туннельный адаптер Подключение по локальной сети* 6:

       Состояние носителя. . . . . . . . : Носитель отключен
       DNS-суффикс подключения . . . . . :
       Описание. . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Физический адрес. . . . . . . . . : 02-00-54-55-4E-01
       DHCP включен. . . . . . . . . . . : Нет
       Автонастройка включена. . . . . . : Да

    Thank you for help.

    Wednesday, February 29, 2012 9:45 AM
  • Unfortunately, I don't know if just unchecking them is enough.  Can you test by uninstalling each of these?  And then I would suggest you uninstall and reinstall the NM3 driver by typing the following at a admin command prompt.  These files are in the program files directory.

    instdrvr.exe /deinstall

    instdrvr.exe /install

    Thanks,

    Paul

    Wednesday, February 29, 2012 4:08 PM