Frequent wireless disconnections occurring since upgrade to 10.21.01.0065

[Steve_Ballantyn]

I apologize for the redundant question. It seems like "clients disconnecting" is a common topic. But I am starting a new one, because it seems that every situation is different.

I have a C5210 and a bunch of 3825i AP's all over my hospital. Just before Christmas I upgraded to the latest firmware, 10.21.01.0065. Since then I am getting complaints from users (across the board) that they are frequently getting dropped from WiFi. After it happens they are easily able to reconnect and all is well. But it's driving them mad as they will be in mid-sentence documenting in their various applications and then it sort of freezes up and KAPOW! Connection lost!

There is nothing newer to upgrade to. And I suppose I could downgrade to see if the problems goes away. But I would rather seek out the source of the problem and fix it. Especially if it's just something wacky in my configuration.

I plan on putting in a call and opening a ticket on Monday morning with support. But in the meantime - does anyone have any ideas for me? I use Netsight and Purview, and I have all of these logs and diagnostic data at my disposal, but I am not really sure where to start. I suppose the first question is - does anyone else have this issue with this firmware?

[Steve_Ballantyn]

I will be updating the wireless drivers today on the affected devices. But in the meantime, here is some more information.

I had a user who got dropped this morning at approximately 9:15AM EST. I think she may have been disconnected several minutes earlier, and didn't realize there was an issue until 9:15AM EST when the device was rejoining.

Here is a snapshot of the client events ....

And here are some log snippets.

What do you all think?

[Drew_C]

Sounds like I can mark this one "Solved," right Steve? 

[Steve_Ballantyn]

Not just yet! Let me see what happens after I update the client drivers later today.

[Steve_Ballantyn]

Oh boy. I might be eating my hat on this one as it may have nothing to do with Extreme and everything to do with Windows 10, a horrible update, and outdated drivers from the manufacturer.

It appears that these laptops (all of them that were reported to me) were taken out of the box and carried into production. Windows Update was on, and was left on. So it has been taking the updates and installing them on it's own (including that dreaded anniversary update). However - nobody ever updated the drivers.

The laptops use Intel Proset wireless, and the drivers were dated February of 2015. Ouch. Also the "allow this device to sleep to save power" appears to be enabled.

So perhaps I have been fighting this from the wrong end! I started doing a little more digging when I went into the event logs of one of the laptops and found these events ... the most telling of which say "WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter".

Level Date and Time Source Event ID Task Category

Error 01/27/2017 10:06:04 AM Microsoft-Windows-WLAN-AutoConfig 4003 None "WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter.

Code: 8 0x0 0x0

"

Information 01/27/2017 10:06:03 AM NETwNb64 7036 None The \Device\NDMP71 service entered the Intel(R) Dual Band Wireless-N 7260 state.

Information 01/27/2017 10:06:01 AM NETwNb64 8000 None "The description for Event ID 8000 from source NETwNb64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\NDMP65

Intel(R) Dual Band Wireless-N 7260

The specified resource type cannot be found in the image file

"

Error 01/27/2017 10:05:59 AM Microsoft-Windows-WLAN-AutoConfig 4003 None "WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter.

Code: 2 0xDEADDEED 0xEEEC

"

Error 01/27/2017 10:05:59 AM Microsoft-Windows-WLAN-AutoConfig 4003 None "WLAN AutoConfig detected limit connectivity, performing Reset/Recover.adapter.

Code: 1 0xC 0x4

"

[Steve_Ballantyn]

Yeah, but I had another device doing this under excellent coverage and I think it was a roaming issue. When I used time-lapse under Netsight, I could see that the laptop was being rolled (on a cart) past two other access points before disconnecting and then trying to reconnect. When I updated the drivers (another from something like 2015) it started roaming properly.

Before I updated the drivers on that laptop which I think was a Samsung, I took screenshots of ALL the wireless settings. I wanted to go back and compare them after updating the drivers to see if the manufacturer tweaked anything. But I have yet to get my hands back on it.