topic Re: Client b cannot associate with ap (in WLC environment) in Wireless

Client b cannot associate with ap (in WLC environment)

phatrachit — Sun, 04 Jul 2021 00:30:34 GMT

I have clients b and g in my network, clients g work properly.

My problem are

1.Client b cannot associated with ap though i manually set SSID on notebook. The notebook supported b only

2.I was setting data rating all of b range (1,2,5.5,6,9,11) are mandatory and g range are support.

3.All of SSIDs not broadcast in the network and user will get SSIDs from AD's policy.

4.Clients b were updated the last driver.

5.I was installed netstrumbler on notebook for probing the network but it cannot see APs MAC address that belong to my network

6.I try to sniffer packet with wireshark but it's show empty result, no packets there.

7.WLC version software is 5.1.151.0

Leo Laohoo — Tue, 28 Apr 2009 23:31:28 GMT

What are the models of your AP's?

Is this the ONLY client using "B"?

phatrachit — Tue, 28 Apr 2009 23:51:15 GMT

- AP model is 1121g

- This client is support B only (old notebook model).

Leo Laohoo — Wed, 29 Apr 2009 00:05:44 GMT

Are there any "B" clients successfully associated?

Is the b/g radio enabled on the WLC?

Have you tried to use other notebooks to use the "B" to associate or identify (using Netstumbler)?

phatrachit — Wed, 29 Apr 2009 00:08:41 GMT

- No B clients successfully associated.

-Already enabled.

Leo Laohoo — Wed, 29 Apr 2009 00:27:26 GMT

How about other AP's?

Can other clients associate using the "B" radio? Have you tried it?

Robert.N.Barrett_2 — Wed, 29 Apr 2009 03:24:50 GMT

On the controller, try setting just the 1 & 2 Mbps speeds as mandatory.

Be sure that the radio policy in your WLAN definition is set to 802.11b/g.

You aren't using WPA2/AES encryption, are you? Old 802.11b clients won't support that.

phatrachit — Wed, 29 Apr 2009 03:25:39 GMT

All of APs are controlled with Wireless controller. It's not autonomous system.