topic Re: Terminals bouncing between AP's in Wireless

Terminals bouncing between AP's

tcherry — Sat, 03 Jul 2021 20:32:36 GMT

We just installed WCS, 2 WLC 4402's with 29 1131 AP's. I have a user who is half way between 2 AP's. He keeps bouncing between the 2 AP's and gets a pop up message each time he does. He has an IBM T43 with a built in wireless card. How can I keep him associated just to one of the AP's. He is a Director so this is a big issue for him. I do not see anything in WCS or the WLC to designate a client to a specific AP. Any help on this would be great.

Re: Terminals bouncing between AP's

scottmac — Tue, 30 Jan 2007 00:21:01 GMT

Are you using the PRoSet software, or Microsoft Zero Wireless Config?

I believe the Intel client utility software will permit you to set the roaming threshold (up in this case).

Good Luck

Scott

Re: Terminals bouncing between AP's

tcherry — Tue, 30 Jan 2007 15:28:33 GMT

We are using the Microsoft Zero config. I will see if the INtel utility will let me do that.

Re: Terminals bouncing between AP's

tcherry — Tue, 30 Jan 2007 18:02:01 GMT

Under the Intel card properties there was a Roaming Agressively option, by unchecking the default if I moved the slide bar to a lower setting the card is more sticky to a AP. The higher setting causes the card to always move to the stronger signal so ther is much more roaming. Thanks for your help. Something else I noted was that by default the card is set to connect 802.11g over 802.11a.

Re: Terminals bouncing between AP's

levenson — Wed, 31 Jan 2007 21:44:19 GMT

There are two things that you can check 1.ensure that you don't have two much overlap

2.The second thing that you can do is go into the client configuration and change the roaming tendencies. Sometimes if your overlap is too great between cells it will cause the client if not set correct to constantly beacon looking for the "best signal" hope this helps

Re: Terminals bouncing between AP's

wififofum — Thu, 29 Mar 2007 00:38:39 GMT

tcherry,

Did you ever get around this issue? One other question: why isn't IP mobility working to preserve the client IP address? The link would have to be down for 4-7 seconds for the OS to detect a L2 drop. Plus there's got to be some way to disable the pop-up.