KB2986895 – VMs Lose Network Connection on WS2012 or WS2012 R2 Hyper-V When Using Broadcom 1GbE NICs

If you’re affected by this issue then you should have read this post. Microsoft posted a KB article for when virtual machines lose network connectivity when you use Broadcom NetXtreme 1-gigabit network adapters on Windows Server 2012 Hyper-V or Windows Server 2012 R2 Hyper-V.


When you have Hyper-V running on Microsoft Windows Server 2012 or Windows Server 2012 R2 together with Broadcom NetXtreme 1-gigabit network adapters (but not NetXtreme II network adapters), you may notice one or more of the following symptoms:

  • Virtual machines may randomly lose network connectivity. The network adapter seems to be working in the virtual machine. However, you cannot ping or access network resources from the virtual machine. Restarting the virtual machine does not resolve the issue.
  • You cannot ping or connect to a virtual machine from a remote computer.

These symptoms may occur on some or all virtual machines on the server that is running Hyper-V. Restarting the server immediately resolves network connectivity to all the virtual machines.


This is a known issue with Broadcom NetXtreme 1-gigabit network adapters that use the b57nd60a.sys driver when VMQ is enabled on the network adapter. (By default, VMQ is enabled.)

The latest versions of the driver are 16.2 and 16.4, depending on which OEM version that you are using or whether you are using the Broadcom driver version. Broadcom designates these driver versions as 57xx-based chipsets. They include 5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, and 5780.

These drivers are also sold under different model numbers by some server OEMs. HP sells these drivers under model numbers NC1xx, NC3xx, and NC7xx.


Broadcom is aware of this issue and will release a driver update to resolve the issue. In the meantime, you can work around the issue by disabling VMQ on each affected Broadcom network adapter by using the Set-NetAdapterVmq Windows PowerShell command. For example, if you have a dual-port network adapter, and if the ports are named NIC 1 and NIC 2 in Windows, you would disable VMQ on each adapter by using the following commands:

Set-NetAdapterVmq -Name “NIC 1″ -Enabled $False
Set-NetAdapterVmq -Name “NIC 2″ -Enabled $False

You can confirm that VMQ is disabled on the correct network adapters by using the Get-NetAdapterVmq Windows PowerShell command.

Note By default, VMQ is disabled on the Hyper-V virtual switch for virtual machines that are using 1-gigabit network adapters. VMQ is enabled on a Hyper-V virtual switch only when the system is using 10-gigabit or faster network adapters. This means that by disabling VMQ on the Broadcom network adapter, you are not losing network performance or any other benefits because this is the default. However, you have to work around the driver issue.

Get-NetAdapterVmqQueue shows the virtual machine queues (VMQs) that are allocated on network adapters. You will not see any virtual machine queues that are allocated to 1-gigabit network adapters by default.

Sigh. I hope Broadcom are quicker about releasing a fix than Emulex (customers are waiting 10 or 11 months now?).

Please follow and like us:

48 Comments on KB2986895 – VMs Lose Network Connection on WS2012 or WS2012 R2 Hyper-V When Using Broadcom 1GbE NICs

  1. Dusan Reznicek // July 28, 2014 at 11:20 AM // Reply

    Hi Aidan, I have a 3 node Hyper-V cluster up on WS2012 with only Intel 1 gigabit adapters. Here’s Get-NetAdapterVmq output from one of the nodes – http://1drv.ms/1kiEMuG and VMQ is enabled. Fortunately I’m not having any issues described above with Broadcom adatpers, but I’m curious why is that :-)


  2. Broadcom Network adapters have historically been hit or miss. At my work, ESXi boxes have had issues with them, we have had Windows 2008 R2 SQL/Exchange servers that have issues and all those issues would clear up when replaced with Intel/Cisco cards.

    We finally got to point where we just order Intel cards in all new Dell boxes and call it a day.

  3. Mathieu Isabel // July 28, 2014 at 7:11 PM // Reply

    FYI We’re experiencing similar symptoms but with 10Gb Broadcom adapters and some of our VMs. It seems that older OS i.e. 2008 R2 and prior are affected. Restarting the guest OS doesn’t resolve anything but switching the network adapter to DHCP then set back again its static IP resolves the issue for us for some odd reason. Looks like something wonky is happening in the integration services/drivers for the vNIC.

    We haven’t tried disabling VMQ yet on the physical adapters. Maybe something to explore.

  4. Andrzej P. // July 29, 2014 at 8:45 PM // Reply

    That would explain a lot… I had that issue a few times with my NICs integrated in Dell R420 :/ I’ve had them in a team in WS2012R2 cluster node and I would loose all network connectivity to all VMs and the node. Though I did not need to reboot the server – in my case I had NICs in team as active-backup and I just needed to change active NIC to restore connectivity (logged in with idrac :) ). I see it’s a good thing we switched to Intel NICs.

    btw. I had another NIC in server for cluster only network and I wondered why that was working…

  5. We are currently experiencing this issue and I was going to disable VMQ this weekend.

    Do you know if the command needs to be run on the NIC team or just the NIC’s that are members of the team?

    Any advice appreciated.

  6. it seems that that the works. We run that with VMQ and have no issues.

    • The advice from MSFT is to disable VMQ on NICs less than 10 Gbps. In fact, I believe some of them were surprised that VMQ is enabled on some 1 GbE NICs by default.

  7. I am running and still have the problem when running VMQ. Am trying to run VDI under XenDesktop and half or more of the the VMs keep dropping off the deliver group (“Unregistered”) after successfully registering initially. I will try disabling VMQ on all pNICs like you said. is still the latest available driveer from Broadcom, correct?

  8. Updated 2 hosts (Drivers – Firmware etc) a few weeks ago and have been seeing this random issue since. Thankfully it was only affecting one port on the NIC that was on the vNIC, and it wasn’t a critical port. Access could be restored by flipping the Port on the switch.

    Upon using Get-NetAdapterVmq – I could see that the problematic port was the only one with VMQ enabled. I’ve now disabled VMQ for that and will report back the results…….

  9. Hi ,
    I have nic 1 & 2 are in teaming in hyper v core os . team name is i have to write in command or just disable the 2 nic one by one?

  10. does disabling VMQ – require reboot ? or disconnect of NICS ?

  11. Hi,

    We was experiencing the same behaivor.

    The problem has been solved with upgrading iDRAC7 from 1.56.55 version to 1.66.65.

    Note from Dell website:
    2.Intermittent connection issues with iDRAC shared LOM network port.


    Hope it will help you guys.

  12. I m experience same behavior in one windows 2003 R2 VM on Hyper v 2012 R2 Failover Cluster . VM nic loose connectivity , VMQ is diasble on Physical Nic please advice ..

  13. Hi

    Please suggest , we have deployed Windows server 2012 R2 termail services on hyper v 2012 R2 Failover Cluster , we have facing slow login issue on user side , stuck on applied group policy , some hangs ….VMQ is diable on Physical NIC ..
    Your quick response is highly appreciated

  14. Kevin Bermingham // April 13, 2015 at 8:08 PM // Reply

    Hey Aidan,

    Yea I’m having this on the HP Proliant DL360p GEN 8 server. It’s the exact driver file name as highlighted on the article above. It’s killing me, I thought it was something I had screwed up on the config but it has to be this issue!!… I hope!

    Are there any other drivers available yet that I can install does anyone know?

    I will disable VMQ in the morning when I get in…. fingers crossed this will sort it

    Thanks for the article …. hopefully this will save my life ; )


  15. Hi Aidan,

    Same situation here, disabled VMQ on the physical NIC however curious as to what affect that has on throughput. There should be still some offload with RSS remaining enabled?

    With 1GB NICs what is the effective throughput we should be seeing between VM on separate hosts?


  16. Matty Brown // May 25, 2015 at 7:59 PM // Reply

    Thanks for the tip. We’re got three Dell PowerEdge R520’s with Broadcom NetXtreme 5720 dual port adapters running Windows Server 2012 R2 and Hyper-V. We’ve been experiencing intermittant network connectivity issues and occassionally the host and one or more guests would lose connectivity to the network, even though everything seemed to be okay.

    After reading your article and Microsoft’s KB2986895 article, I decided to give your fix a go, using the following PowerShell commands:

    Set-NetAdapterVmq -Name “NIC1″ -Enabled $False
    Set-NetAdapterVmq -Name “NIC2″ -Enabled $False
    Set-NetAdapterVmq -Name “NIC Team″ -Enabled $False

    I haven’t had a problem since – touch wood – and it’s been almost a week.

    Our NICs are all running the latest firmware and drivers as of now (25/05/2015)… unfortunately, Dell/Broadcom haven’t fixed the issue yet, but since I don’t notice any downside to switching VMQ off and our servers are now running without networking issues, I’m no longer bothered.

    • Good. There is no downside to disabling VMQ on 1 Gbps NICs – Microsoft has told the OEMs to do this and they were ignored.

  17. Hi
    We’ve had the same issue with our 7node HV Cluster of 2012R2 -all with 1Gbit Broadcoms. First I’ve disabled TCP Offload on all NICs and that kinda fixed the issue until now (2 months later). As it seems the only enabled interfaces were two out of 3 designated for VM traffic.

    For all those that have more than 1 host and would like to do it remotely here’s how – replace HVHOST1 atc with your HV host name.

    $HVHosts = (“HVHOST1″,”HVHOST2″)

    Invoke-Command $HVHosts -ScriptBlock {
    Get-NetAdapterVmq | % {
    if ($_.Enabled -eq ‘True’) {Set-NetAdapterVmq $_.Name -Enabled $false}

    Thanks Aidan for the information. Will report back in a while to see if that work longterm:)

    BTW. here’s my set of “disablers” for HV Host on 1 Gbit Broadcoms. I have 4 built in NICs (Named NIC1-4) and two PCI slots with 4 nics each named PCI1_1 to PCI1_4 and PCI2_1 to PCI2_4). They differ with feature set so different commands for each group. Also disabling that on Microsoft teaming interfaces.

    $NICs = Get-NetAdapter -Name NIC*
    foreach ($NIC in $NICs) {
    Set-NetAdapterAdvancedProperty $NIC.name -RegistryKeyword *LsoV2IPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $NIC.name -RegistryKeyword *LsoV2IPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $NIC.name -RegistryKeyword *TCPConnectionOffloadIPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $NIC.name -RegistryKeyword *TCPConnectionOffloadIPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $NIC.name -RegistryKeyword *TCPUDPChecksumOffloadIPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $NIC.name -RegistryKeyword *TCPUDPChecksumOffloadIPv4 -RegistryValue 0

    $PCIs = Get-NetAdapter -Name PCI*
    foreach ($PCI in $PCIs) {
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *LsoV1IPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *LsoV2IPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *LsoV2IPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *UDPChecksumOffloadIPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *UDPChecksumOffloadIPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *TCPChecksumOffloadIPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *TCPChecksumOffloadIPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $PCI.name -RegistryKeyword *IPChecksumOffloadIPv4 -RegistryValue 0

    $Teams = Get-Netadapter -InterfaceDescription “*Multiplex*”
    foreach ($Team in $Teams) {
    Set-NetAdapterAdvancedProperty $Team.name -RegistryKeyword *LsoV2IPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $Team.name -RegistryKeyword *LsoV2IPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $Team.name -RegistryKeyword *IPChecksumOffloadIPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $Team.name -RegistryKeyword *UDPChecksumOffloadIPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $Team.name -RegistryKeyword *UDPChecksumOffloadIPv6 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $Team.name -RegistryKeyword *TCPChecksumOffloadIPv4 -RegistryValue 0
    Set-NetAdapterAdvancedProperty $Team.name -RegistryKeyword *TCPChecksumOffloadIPv6 -RegistryValue 0

    Not using TCPv6 to V4 so disabling that as well.

    Set-NetTeredoConfiguration -Type Disabled
    Set-NetIsatapConfiguration -State Disabled
    Set-Net6to4Configuration -State Disabled

    Disabling VMQ on all enabled interfaces:

    Get-NetAdapterVmq | % { if ($_.Enabled -eq ‘True’) {Set-NetAdapterVmq $_.Name -Enabled $false} }

  18. John Hagan // June 9, 2015 at 3:55 PM // Reply

    I’ve got two Dell PowerEdge R530 server with Broadcom NetXtreme 5720 dual port adapters running Windows Server 2012 R2 and Hyper-V. I have updated to the latest firmware (7.10) and driver (the “19.0 update”, which shows driver version “” in the Windows device manager after being installed) published on Dell’s support web site (Release date 07 Apr 2015). If I don’t turn of VMQ by using the ‘Set-NetAdapterVmq -Name “NIC1″ -Enabled $False’ PowerShell command, the adapter goes deaf until reset if put under load (such as copying large files across the network), exactly as described in KB2986895.

    So it appears I can confirm that the latest Broadcom drivers don’t fix this issue. Fortunately, the disabling of VMQ described in KB2986895 still resolve the issue (at least for my configuration).

  19. Hmm, disabling VMQ with the powershell doesn’t seem to have any effect. Should try to disable the tcp offload and other settings as scripted above. Note to mention that with 10gb Qlogic extremes the driver side will still have the VMQ enabled. Disabling this doesn’t help either. Just constant loss of connectivity on the host side.

  20. Is the command set-netadaptervmq -name “…” -enabled $false permanently or must I repeat that after each server restart


    Uwe Weih

  21. Just another update for people still having this problem – I’m running a five-node cluster on HP DL380 Gen9 servers with these NICs, and we’ve updated through three different versions of the driver that claim to fix this problem (16.8, 17.0, 17.2), but to no avail. I’m now disabling VMQs on the physical NICs, so hopefully I can finally draw a line under it.

  22. Damian Sleger // October 30, 2015 at 7:45 PM // Reply

    Just FYI- I opened a support incident with Microsoft yesterday regarding this very issue. I’m running a cluster of 8 HP DL360p Gen8 and 9’s (2012 R2 Core), using the HP Emulux 10gb adapters, newest drivers and firmware, all Winders updates are installed as well as MS recommended HV-specific patches. MS had me disable VMQ this morning, so far so good. I just wanted to let you know this isn’t a Broadcom exclusive issue.

    • The Emulex issue is well known – see Hyper-v.nu for more. Have you deployed the latest drivers and firmware for your NICs from HP? This was supposed to have been fixed earlier this year by them. There was also an update via Windows Update to fix the last little bits in the MSFT networking stack.

      • Aidan, thanks for the reply. As long as I got you, I’d like to thank you for all the help your site has given me over the years.

        Yep, my NIC driver/firmware is current, and I have all Windows updates installed & current.

      • You wouldn’t happen to have the exact URL on Hyper-v.nu, would you? I dug around and couldn’t find anything emulex specific.

  23. Hi,

    One of my Windows Server 2012 r2 VM is also having same issue. From the VM some IP’s are accessible & other’s are not. Having Intel I350 Gigabit adapter on host server.

    Tried to disable VMQ on this VM but that also didn’t resolve this issue.


    • Disable VMQ on the physical NICs. Also ensure that drivers & firmware are up to date for the physical NICs and that the host is patched.

2 Trackbacks & Pingbacks

  1. blog.atwork.at | CDP-B329 - From Demo to Reality: Best Practices Learned from Deploying Windows Server 2012 R2 Hyper-V - TEE14
  2. Broadcom QLogic VMQ Hyper-V Network Bug | Notes by Tom

Leave a comment

Your email address will not be published.