11-11-2011 04:23 PM - edited 07-03-2021 09:03 PM
Just recently upgrade our 2 5508 controllers from 6.0.199.0 to 7.0.116.0. Since that upgrade, I have a handful (8 to 10) of wireless laptops that now refuse to associate to any access points. The thing these laptops all have in common is some variation of the Intel Wifi Link AGN cards. I have about 200 other clients out there working just fine.
I've tried everything under the sun that I can think of. Patches, drivers, the whole sh'bang.
Is there a known issue with 7.0.116.0 and these particular cards? I'm really stumped.
Thanks all!
11-11-2011 04:34 PM
Errrr .... How about try the newer 7.0.220.0?
11-11-2011 04:37 PM
That is weird. So do some of the other devices that connect have these same wireless cards or have you isolated the issue to that card?
Sent from my iPhone
11-11-2011 10:22 PM
Also now discovered that no Apple Airbooks can connect to the wireless now either. Weird.
I'll see about going to the 220 code.
11-11-2011 10:32 PM
Odd, I seen similar behavior. When I enabled fast ssid i noticed the devices would connect .. try that
11-12-2011 12:44 AM
Make sure client load balancing is disabled on the WLAN SSID advanced tab on the lower right side of the page. This feature doesn't play well with Apple devices and various other laptops.
Sent from my iPhone
11-11-2011 10:36 PM
Wat does the debug client say??
11-12-2011 06:03 AM
Do you have Aironet enabled on your SSID?
Sent from Cisco Technical Support iPhone App
11-12-2011 07:54 AM
'Aironet IE' is enabled on the SSID
'Client load balancing' is disabled
I tried the 'fast ssid'...no change.
I've never done a debug client...I have to be on the controller console to do that, right?
Thanks all!
11-12-2011 09:04 AM
Just the telnet session will do it!! console is not mandatory to run the debug
The debug will be
debug client
Regards
Surendra
11-12-2011 08:17 AM
Try disabling Aironet, let me know if that fixes your issue
Sent from Cisco Technical Support iPhone App
11-14-2011 07:58 AM
The solution turned out to be, disable/enable the b/g/n radios on each controller. Once we did that, all of the clients could connect again. So strange.
Thanks to all for the suggestions!
11-14-2011 02:38 PM
Strange!!
Regards
Surendra
11-14-2011 02:56 PM
The solution turned out to be, disable/enable the b/g/n radios on each controller. Once we did that, all of the clients could connect again.
><
11-14-2011 08:04 PM
Sounds like CSCto93293 that we discovered and worked with TAC to diagnose. The notes talk about the 1140 but is present in all AP. 7.0.220.0 fixes
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide