Data rate will not exceed 54 Mbps when WEP or TKIP encryption is configured

[Craig Le-Butt]

Hi

Just playing around with some wireless cards and found having issues with getting high speed with 802.11n.

After looking found can't get high speeds becouse we are still using WEP-TKIP encrytion.

This is ther becouse of XP SP2 limitations many moons ago

Our config on WLC

802.1x

with WEP-TKIP

WPA2-AES

We can remove the WEP-TKIP from the group policy for windows.

I want to double check and get a 100% right is the this will allow a device to connect via WEP-TKIP or WPA2-AES.

So removing the setting from the group policy will so only laptops connect via wpa2-aes will still work if I leave these WEP-TKIP in when the windows device only has wpas-aes settings?

cheers

[Scott Fella · Accepted solution]

802.11n only supports open authentication or the use of WPAv2 with AES. Having both WPA v1/TKIP and WPA v2/AES on the same SSID has been known also to cause issues with WLCs. If you have devices that only support WPA v1/TKIP, then there is nothing you can do for those devices. They are two different encryption types... If you remove WPA/TKIP then clients that are configured to use that will not connect to WPAv2/AES.

Sent from Cisco Technical Support iPhone App

[Craig Le-Butt]

Hi Scott

Thanks for that, this was left in for the legacy laptop and PDAs, that are no longer on the wlan.

just need to change the group policy for change them to wpa2-aes only instead of iether.

Just didn't want 800 devices have to connect to the lan and force a group policy via gpupdate.

Cheers

[Scott Fella]

Sometimes it's better to create a new SSID so you can migrate users to that new on and eventually decommission the old SSID. The issue with pushing out group policy to change the existing is what happens when users are not in the office or their device doesn't support WPA v2/AES. Now your help desk will be stuck working with these users. If you push out another wireless profile and put the new one as priority, well then you still have the old SSID to fall back to. The issue with pushing out a new SSID also is you need to determine what devices can support WPA v2/AES and maybe only push the policy to those devices.

Sent from Cisco Technical Support iPhone App