none
Problem installing Network Monitor on Windows 2008 R2 RRS feed

  • Question

  • I'm trying to install Network Monitor 3.3 on Windows 2008 R2.
    It's a x64 machine, Intel Xeon

    During the install, the system hangs on "Binding Netmon Driver"
    The only way to recover is to hard reset the server.

    Some more info I found

    I'm installing Network Monitor on a VMWare Guest.
    If I change the guest settings to be NAT (and not bridged), I can install it and everything works fine.
    As soon as I change to Bridged, Windows doesn't even boot and hang during the boot.
    The physical network card is a Broadcom BCM5709C.

    Any help much appreciated

    Here is the last couple of lines from the install log:

    MSI (s) (04:BC) [12:37:42:944]: Executing op: UpgradeCodePublish(UpgradeCode={8F53AE81-8496-4E17-9127-605424FE249C})
    MSI (s) (04:BC) [12:37:42:945]: Executing op: SourceListPublish(,,DiskPromptTemplate=Microsoft Network Monitor Installation [1],,NumberOfDisks=1)
    MSI (s) (04:BC) [12:37:42:945]: Note: 1: 1402 2: UNKNOWN\Installer\Products\01A5C5631656F4549B5765AE78D8A060\SourceList 3: 2 
    MSI (s) (04:BC) [12:37:42:947]: Executing op: ProductPublishClient(,,)
    MSI (s) (04:BC) [12:37:42:948]: Executing op: SourceListRegisterLastUsed(SourceProduct={365C5A10-6561-454F-B975-56EA878D0A06},LastUsedSource=C:\Users\PIETER~1\AppData\Local\Temp\IXP000.TMP\)
    MSI (s) (04:BC) [12:37:42:948]: Entering CMsiConfigurationManager::SetLastUsedSource.
    MSI (s) (04:BC) [12:37:42:949]: Specifed source is already in a list.
    MSI (s) (04:BC) [12:37:42:949]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (04:BC) [12:37:42:949]: Adding new sources is allowed.
    MSI (s) (04:BC) [12:37:42:949]: Set LastUsedSource to: C:\Users\PIETER~1\AppData\Local\Temp\IXP000.TMP\.
    MSI (s) (04:BC) [12:37:42:949]: Set LastUsedType to: n.
    MSI (s) (04:BC) [12:37:42:949]: Set LastUsedIndex to: 1.
    MSI (s) (04:BC) [12:37:42:949]: Executing op: ActionStart(Name=BindDriver,Description=Binding Netmon Driver,)
    Action 12:37:42: BindDriver. Binding Netmon Driver
    MSI (s) (04:BC) [12:37:42:951]: Executing op: CustomActionSchedule(Action=BindDriver,ActionType=3106,Source=C:\Program Files\Microsoft Network Monitor 3\,Target="C:\Program Files\Microsoft Network Monitor 3\nmconfig.exe" /install S-1-5-21-2578263067-1492562331-216794716-1158,)

     

     

    Friday, April 9, 2010 5:00 PM

Answers

  • Michael, thank you for this information. I've downloaded the beta, but before I could try it our IT team decided to revert to Windows 2008 SP2 as apposed to R2. The reason is that VMWare server 2.0.2 does not officially support Windows 2008 R2 and hence finding support on the forums or from VMWare is a nightmare.

    For what it's worth, Network Monitor 3.3 now works perfectly fine with no strange hangups etc. Most likely it was never a Network Monitor issue to start with.

    If we get some time - I'll bring up one of the R2 images and put the beta version on there to see if it changes anything.

    Pieter.

     

    • Marked as answer by Pieter Venter Tuesday, April 20, 2010 1:27 PM
    Tuesday, April 20, 2010 1:26 PM

All replies

  • Hi Pieter,

    Thanks for reporting this issue to us.  I'm having our test team take a look at it to see if they have any suggestions, but I know we do more testing with Hyper-V over VMWare.

    I'll let you know if we could use any more information from the log, but it might also help us if you can explain your scenario in a bit more detail (i.e. the need for a bridged vs. NAT connection).


    Michael Hawker | Program Manager | Network Monitor
    Friday, April 9, 2010 10:12 PM
    Moderator
  • The virtual machine exposes some software on the Internet (web server and others) and hence bridged networking is the best fit.

    I've narrowed the problem down to a bridged vs. Nat scenario.

    If I set the VM to NAT - I can install Network Monitor inside the VM, uninstall etc.
    If I set the VM to Bridged - it hangs on the Binding Netmon Driver step.

    I'm happy to expose the whole install log to you if that will help. Just let me know where I can send it to.

    My gut feel is this is something particular to the host since I've had this exact same scenario (guest with bridged networking) running just fine - although it was on a different host hardware. Also, the fact that changing settings (bridged vs nat) on the host causes the guest to succeed or fail makes me think it has to be a problem "outside".

    I've upgraded the Dell server with the latest drivers etc. but still no luck. I want my NetMon back - can't really live without it!

    Monday, April 12, 2010 3:59 AM
  • Pieter, to send us the log use the email link on left margin on http://blogs.technet.com/netmon to start a conversation.  Once I respond, you'll have my email address and you can attach the log file and we can take a look.

    The fact that it works on one VM and not another might be hard for us to figure out.  I'm not sure what the best way to compare VMWare installs, but perhaps there's a tool you can output the configuration with to determine what might be different (Version, drivers, etc).  But perhaps the logs will also give us a clue.

    Thanks,

    Paul

    Friday, April 16, 2010 2:35 PM
  • Pieter,

    You can also try the 3.4 Beta available to our registered Connect members at http://go.microsoft.com/fwlink/?LinkID=143947.

    Let us know if it still reproduces the problem as well.


    Michael Hawker | Program Manager | Network Monitor
    Friday, April 16, 2010 6:44 PM
    Moderator
  • Michael, thank you for this information. I've downloaded the beta, but before I could try it our IT team decided to revert to Windows 2008 SP2 as apposed to R2. The reason is that VMWare server 2.0.2 does not officially support Windows 2008 R2 and hence finding support on the forums or from VMWare is a nightmare.

    For what it's worth, Network Monitor 3.3 now works perfectly fine with no strange hangups etc. Most likely it was never a Network Monitor issue to start with.

    If we get some time - I'll bring up one of the R2 images and put the beta version on there to see if it changes anything.

    Pieter.

     

    • Marked as answer by Pieter Venter Tuesday, April 20, 2010 1:27 PM
    Tuesday, April 20, 2010 1:26 PM
  • Thanks Pieter,

    Keep us posted if you find anything.


    Michael Hawker | Program Manager | Network Monitor
    Tuesday, April 20, 2010 7:42 PM
    Moderator
  • Hello.  Do you have a copy of NetMon 3.3 64-bit version?  I have the same installation problem on a WS 2008 R2 guest machine.  Thanks.

     

    Wednesday, July 28, 2010 12:22 AM
  • Network Monitor 3.4 is the latest released version now and you should use it.  It's availalbe on the download center.

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f

     

    Wednesday, July 28, 2010 1:51 PM
  • I faced same problem with Windows 10, Network Monitor 3.4 hanged at same installation step.

    In my case I didn't hang if I eliminated all unidentified networks.

    My setup is VitrualBox and 8 virtual adapters; two of them were NATs, the others were set to `null`. Before I faced this, all 8 adapters had "link" ("cables" were "connected") and installation hanged. When I "unplugged" "cables" from 6 unused adapters, Network Monitor could be installed flawlessly.

    Tuesday, December 18, 2018 7:21 PM