Corrupted or outdated device driver could be a reason for Broadcom 802.11n Network Adapter not working. You can fix the issue by updating your Broadcom 802.11n Network Adapter driver on Windows 10. Here is how to do it. Horiba usb devices driver. Step 1: Right-click Start and choose Device Manager. Step 2: In the pop-up window, double-click Network adapters to extend it. Download drivers for Broadcom 802.11n Network Adapter. Drivers found: 4. To download the drivers, select the appropriate version of driver and supported operating system. Broadcom is aware of this issue and will release a driver update to resolve the issue. Until the driver update is available, you can work around the issue by taking one of the following actions: Disable VMQ on the Virtual Network Adapter by using the following Windows PowerShell cmdlet.
At the 'Broadcom 802.11n Network Adapter Ver. 6.30.9.44' screen, click 'Next'. At the 'License Agreement' dialog, read the agreement, then, if you agree, click 'I Agree' to continue with the installation. At the 'Finished' screen, click 'Finish'.
-->This article provides a workaround for an issue that occurs if you have a Windows Server 2012 Hyper-V host that uses a Broadcom network adapter.
Original product version: Windows Server 2012 R2
Original KB number: 2902166
Symptoms
Consider the following scenario:
- You have a Windows Server 2012 Hyper-V host that uses a Broadcom network adapter.
- You create a virtual switch that binds to the network adapter.
- You enable virtual machine queue (VMQ) on the Hyper-V host.
In this scenario, you experience poor network performance on the virtual machines that are hosted on the Hyper-V host.
Cause
This is a known issue with Broadcom network adapter drivers when VMQ is enabled. The following Broadcom network adapters are affected:
- 57712
- 57800
- 57810
- 57840
Resolution
Broadcom is aware of this issue and will release a driver update to resolve the issue. Until the driver update is available, you can work around the issue by taking one of the following actions:
Disable VMQ on the Virtual Network Adapter by using the following Windows PowerShell cmdlet:
Note
If the problem is not solved, disable VMQ on the Broadcom network adapter.
Change the Media Access Control (MAC) address of the virtual switch.
Note
IP address of the Hyper-V host may change if DHCP is used.
If you use System Center Virtual machine Manager (SCVMM), SCVMM can automatically assign a new MAC address.
To manually assign a MAC address, follow these steps:
Assign a MAC address by using the following Windows PowerShell cmdlet:
Assign a dynamically generated MAC address by using the following Windows PowerShell cmdlet:
- If there's another unaffected network adapter on the Hyper-V host, bind the virtual switch to that network adapter.
Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
-->Broadcom Network & Wireless Cards Drivers
This article provides a solution to an issue where virtual machines lose network connectivity when you use Broadcom NetXtreme 1-gigabit network adapters.
Original product version: Windows Server 2012 R2
Original KB number: 2986895
Symptoms
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.
Cause
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 by the Broadcom network driver.)
Broadcom designates these network adapters as 57xx based chipsets. They include 5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, and 5780.
These network adapters are also sold under different model numbers by some server OEMs. HP sells these drivers under model numbers NC1xx, NC3xx, and NC7xx. You may be using driver version 16.2, 16.4, or 16.6, depending on which OEM version you are using or whether you are using the Broadcom driver version.
Resolution
This issue is resolved in Broadcom driver b57nd60a.sys version 16.8 and newer. In March 2015, Broadcom published driver version 17.0 for download. In April 2015, HP published version 16.8 of the driver for their affected network adapters, contact your server OEM if you need a driver that is specific to your server.
Broadcom Network & Wireless Cards Drivers
If you are unable to update your network adapter driver to resolve the issue, you can work around the issue by disabling VMQ on each affected Broadcom network adapter by using the Set-NetAdapterVmq Polhemus driver. 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:
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 aren't losing network performance or any other benefits because this is the default. However, you need to do this 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.