asked on

Wireless Clients not connecting on preferred standard

I'm not sure if this has to do with the 802.11(a,b,g,n) standard, but the situation is this. We have a wireless network that supports all of these standards using several Cisco Aironet 1200 series APs. We also have a mix of HP NC6220, NC6400, and IBM T61 laptops. The NC6400's have ABG cards but only seem to connect on G unless you specify under the card properties to only use A. Once on A they work fine so I know the setup on the AP is correct. The same thing happens with the T61's which have AGN cards. They never connect to the 5GHz networks unless you tell them to specifically. We've spent the money on AP's with 2.4 and 5GHZ radios, but we only ever seem to use the 2.4 range. Just thought someone might know a tweek or reason for this.

rionroc

Hello

Cisco Aironet 1200 support Network Standard are 802.11a, 802.11b, and 802.11g[only].

Non-overlapping channels in the 5 GHz band (802.11n).

So [Cisco Aironet 1200 Series Access Point] does not allow 5 GHz band (802.11n).

Great is our GOD.
:)

ASKER CERTIFIED SOLUTION

pmwrightjr

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

yorkschool

ASKER

I guess we were hoping that half the clients would use G and the other half would use A and spread the demand over the 2 radios. I will be looking at putting some of the clients on A only and see what happens. You were right about the 1200 Aps we have 4 1200(g), 4 1220(a g), 2 1230 (a g), and 3 new 1250 (a g n). since I don't have complete a coverage it's hard to put people on A only. if you tell the card to connect to A only it connects right away and roams to other APs with A. My overall goal was to distribute the loads but I see what you mean about overall quality of signal as a preferred network.

Thanks,

Dan

pmwrightjr

Dan - Thanks for the additional information. I think there might be a way to accomplish what you want to do by using a combination of group policy and some system-side programming. Since your equipment is all Cisco, it seems like there should be a way to accomplish load-balancing even without a WLAN controller. I'll give it some thought and post back to this thread if I have an idea.