Wireless Access

Hi All,

I'm doing some investigation into a strange issue whereby Windows 10 laptops using Intel 8260/8265 NICs with up to date drivers (20.70.30.1, and some earlier versions) mark their WiFi card as bad until the machine is rebooted. The windows event logs have Netwtw06 Error ID 5010 at the time of the connection dropping. A lot of googling suggests this is quite a common problem but very few solutions beyond the usual upgrade driver, downgrade driver etc etc. We can't downgrade the drivers too far before hitting quite a few major issues with other bugs.

My thoughts are it's a client problem however when the problem arises it occurs on multiple machines connected to the same AP at the same time and only impacts the Intel 8260/8265 Windows 10 laptops, every other device is fine and carries on working. The APs in question are AP-515 connected back to a cluster of 7240XM running 8.7.1.10, clients authenticated with WPA2-Enterprise with either user creds or a cert. It impacts client devices on multiple vlans at the same time although all on a single SSID.  My assumption is this is a problem caused by some rogue frame that's triggering something in the driver it can't handle but exactly what I don't know. I'm yet to get any packet captures - that's tomorrow's job.

We've had two significant changes since this started to occur, the first is the addition of 802.11k in a default configuration and the second is the sudden arrival of 18,000 WiFi clients with limited load testing thanks to pandemics since deploying a lot of Aruba.

Are we alone in seeing this problem or do any of you have a really nice, simple solution to this?

Thanks,

Richard

Hi All,

I'm doing some investigation into a strange issue whereby Windows 10 laptops using Intel 8260/8265 NICs with up to date drivers (20.70.30.1, and some earlier versions) mark their WiFi card as bad until the machine is rebooted. The windows event logs have Netwtw06 Error ID 5010 at the time of the connection dropping. A lot of googling suggests this is quite a common problem but very few solutions beyond the usual upgrade driver, downgrade driver etc etc. We can't downgrade the drivers too far before hitting quite a few major issues with other bugs.

My thoughts are it's a client problem however when the problem arises it occurs on multiple machines connected to the same AP at the same time and only impacts the Intel 8260/8265 Windows 10 laptops, every other device is fine and carries on working. The APs in question are AP-515 connected back to a cluster of 7240XM running 8.7.1.10, clients authenticated with WPA2-Enterprise with either user creds or a cert. It impacts client devices on multiple vlans at the same time although all on a single SSID.  My assumption is this is a problem caused by some rogue frame that's triggering something in the driver it can't handle but exactly what I don't know. I'm yet to get any packet captures - that's tomorrow's job.

We've had two significant changes since this started to occur, the first is the addition of 802.11k in a default configuration and the second is the sudden arrival of 18,000 WiFi clients with limited load testing thanks to pandemics since deploying a lot of Aruba.

Are we alone in seeing this problem or do any of you have a really nice, simple solution to this?

Thanks,

Richard

Hi All,

I'm doing some investigation into a strange issue whereby Windows 10 laptops using Intel 8260/8265 NICs with up to date drivers (20.70.30.1, and some earlier versions) mark their WiFi card as bad until the machine is rebooted. The windows event logs have Netwtw06 Error ID 5010 at the time of the connection dropping. A lot of googling suggests this is quite a common problem but very few solutions beyond the usual upgrade driver, downgrade driver etc etc. We can't downgrade the drivers too far before hitting quite a few major issues with other bugs.

My thoughts are it's a client problem however when the problem arises it occurs on multiple machines connected to the same AP at the same time and only impacts the Intel 8260/8265 Windows 10 laptops, every other device is fine and carries on working. The APs in question are AP-515 connected back to a cluster of 7240XM running 8.7.1.10, clients authenticated with WPA2-Enterprise with either user creds or a cert. It impacts client devices on multiple vlans at the same time although all on a single SSID.  My assumption is this is a problem caused by some rogue frame that's triggering something in the driver it can't handle but exactly what I don't know. I'm yet to get any packet captures - that's tomorrow's job.

We've had two significant changes since this started to occur, the first is the addition of 802.11k in a default configuration and the second is the sudden arrival of 18,000 WiFi clients with limited load testing thanks to pandemics since deploying a lot of Aruba.

Are we alone in seeing this problem or do any of you have a really nice, simple solution to this?

Thanks,

Richard

Hi All,

I'm doing some investigation into a strange issue whereby Windows 10 laptops using Intel 8260/8265 NICs with up to date drivers (20.70.30.1, and some earlier versions) mark their WiFi card as bad until the machine is rebooted. The windows event logs have Netwtw06 Error ID 5010 at the time of the connection dropping. A lot of googling suggests this is quite a common problem but very few solutions beyond the usual upgrade driver, downgrade driver etc etc. We can't downgrade the drivers too far before hitting quite a few major issues with other bugs.

My thoughts are it's a client problem however when the problem arises it occurs on multiple machines connected to the same AP at the same time and only impacts the Intel 8260/8265 Windows 10 laptops, every other device is fine and carries on working. The APs in question are AP-515 connected back to a cluster of 7240XM running 8.7.1.10, clients authenticated with WPA2-Enterprise with either user creds or a cert. It impacts client devices on multiple vlans at the same time although all on a single SSID.  My assumption is this is a problem caused by some rogue frame that's triggering something in the driver it can't handle but exactly what I don't know. I'm yet to get any packet captures - that's tomorrow's job.

We've had two significant changes since this started to occur, the first is the addition of 802.11k in a default configuration and the second is the sudden arrival of 18,000 WiFi clients with limited load testing thanks to pandemics since deploying a lot of Aruba.

Are we alone in seeing this problem or do any of you have a really nice, simple solution to this?

Thanks,

Richard

Hi All,

I'm doing some investigation into a strange issue whereby Windows 10 laptops using Intel 8260/8265 NICs with up to date drivers (20.70.30.1, and some earlier versions) mark their WiFi card as bad until the machine is rebooted. The windows event logs have Netwtw06 Error ID 5010 at the time of the connection dropping. A lot of googling suggests this is quite a common problem but very few solutions beyond the usual upgrade driver, downgrade driver etc etc. We can't downgrade the drivers too far before hitting quite a few major issues with other bugs.

My thoughts are it's a client problem however when the problem arises it occurs on multiple machines connected to the same AP at the same time and only impacts the Intel 8260/8265 Windows 10 laptops, every other device is fine and carries on working. The APs in question are AP-515 connected back to a cluster of 7240XM running 8.7.1.10, clients authenticated with WPA2-Enterprise with either user creds or a cert. It impacts client devices on multiple vlans at the same time although all on a single SSID.  My assumption is this is a problem caused by some rogue frame that's triggering something in the driver it can't handle but exactly what I don't know. I'm yet to get any packet captures - that's tomorrow's job.

We've had two significant changes since this started to occur, the first is the addition of 802.11k in a default configuration and the second is the sudden arrival of 18,000 WiFi clients with limited load testing thanks to pandemics since deploying a lot of Aruba.

Are we alone in seeing this problem or do any of you have a really nice, simple solution to this?

Thanks,

Richard

Hi All,

I'm doing some investigation into a strange issue whereby Windows 10 laptops using Intel 8260/8265 NICs with up to date drivers (20.70.30.1, and some earlier versions) mark their WiFi card as bad until the machine is rebooted. The windows event logs have Netwtw06 Error ID 5010 at the time of the connection dropping. A lot of googling suggests this is quite a common problem but very few solutions beyond the usual upgrade driver, downgrade driver etc etc. We can't downgrade the drivers too far before hitting quite a few major issues with other bugs.

My thoughts are it's a client problem however when the problem arises it occurs on multiple machines connected to the same AP at the same time and only impacts the Intel 8260/8265 Windows 10 laptops, every other device is fine and carries on working. The APs in question are AP-515 connected back to a cluster of 7240XM running 8.7.1.10, clients authenticated with WPA2-Enterprise with either user creds or a cert. It impacts client devices on multiple vlans at the same time although all on a single SSID.  My assumption is this is a problem caused by some rogue frame that's triggering something in the driver it can't handle but exactly what I don't know. I'm yet to get any packet captures - that's tomorrow's job.

We've had two significant changes since this started to occur, the first is the addition of 802.11k in a default configuration and the second is the sudden arrival of 18,000 WiFi clients with limited load testing thanks to pandemics since deploying a lot of Aruba.

Are we alone in seeing this problem or do any of you have a really nice, simple solution to this?

Thanks,

Richard