Client Roaming issues

[klasse]

I have Cisco 1230s in a 6 story building with an atrium. I have 350 b clients using the CISCO ACU and Leap authen. I also have intel 2200BG clients using windows XP client software with PEAP authentication. Since moving to the XP client and the Intel cards my clients roam much more frequently than the 350 cards did with the ACU. I have been told the CCX extensions helped control the client and the XP client does not support the CCX extensions and does not control the intel card like the ACU does with the Cisco 350 card. Anyway, does anyone know how to control roaming better.

For example, my Intel client will be on an access point with 5 clients with -65 dbm signal, then it will roam to an access point with 10 clients on it and -90 dbm for signal strength. Is there anything I can do to control this "BAD" roaming?

-Karl

[radiomen]

well as you probably know the roaming is a choice that the client STA makes. I suggest you investigate more about the intel cards. With the ACU that they probably provide there will be no way to change it unless there is some file to edit to change the -65dbm to a higher or lower value.

[r.marzinzik · Accepted solution]

Hi

I had the same problem in my company. We have also intel 2200BG clients using windows XP with driver version 9.0.1. This Wireless driver has an bad roaming algorythm. After updating to driver version 9.0.2 the problem was solved. You can find the driver on the Intel hompage.

[estein]

We are having the same problem at my company - the Intel 2200BG clients experience frequent disassociations and reassociations, and tend to choose much poorer link qualities in favor of closer APs with better link quality, but the problem is worse when performing WPA authentication as opposed to static WEP.

We upgraded to the newer 9.0.2 drivers but still have the same problems - anyone else experience this, or did 9.0.2 solve everyone's problems?

[jawwalit]

i also use 9.0.2 but doesnt solve the problem

[rhobab]

Try removing the Intel utility and leave only the driver.

[klasse]

we are not using or installing the INTEL client. We are only using the XP SP1 wireless client with most of the wireless fixes.

[durkac]

Similar situation: WPA, PEAP, Win XP SP1 with KB826942, XP build-in client, Intel Software not installed, only driver used, IOS 12.3(4)

With Intel driver 9.0.1.0, the clients roamed a lot and had a lot of connectivity losts.

With Intel driver 9.0.2.0, the situation is better for most users, but still not perfect. Sometimes it takes long to associate, sometimes the connectivity is lost for a short time without moving the device.

We had to deactivate "Update root certificate" in Windows - settings - software - windows components to speed up booting.

[klasse]

This is a side note, but sometimes our XP SP1 clients with 826942 fix will have great signal and be associated and authenticated, but not get an IP address. I am pretty sure it is not the access points nor is it our DHCP server. I almost think this is a timing issue with XP. We are also running 12.3(4) on our 1230 APs.

Has anyone experienced this? Does SP2 fix this?

[djohnson]

I am suffering from the same issue and it started acting up a lot this morning.

Infrastructure: 1120B-A-K9 series AP's with 12.3(2)JA2

Encryption/Authentication:

VLAN 1: WEP128 + TKIP with static key

VLAN 4: WPA + TKIP with EAP-TLS

Devices: Dell Latitude D600, 610 and X1 and some HP Tablets all with Intel cards installed.

The AP's show groups of devices roamining to new AP's and it shows expiring authentication and reassociation messages.

We are moving to the G radios at the end of the month hopefully, but we ordered Cisco direct so it could take a long time for the upgrade kits to arrive.

[estein]

Upgrading the wireless drivers for the Intel 2200BG to v. 9.0.2.31 is key - it solved most of our stability issues with the drivers. I'm wondering though, has anyone been able to automate the upgrade to 9.0.2.31 without wiping out the current wireless profiles? We're struggling with that right now, as the "SetupWLD.EXE" file they provide deletes all current wireless profiles.