AP1200 connection issue

[adam.strobel]

hi-

I use AP1200 access points with Cisco PCMCIA cards for our laptop users and this works fine.

When I try to use a laptop with its built in wirless card, I can only get as far as "Acquiring network address" and eventually it times out.

These are new compaq nc6000 laptops with HP WLAN 802.11a/b/g W500 intergrated wireless cards.

any help would be great!

[thisisshanky]

Try upgrading drivers on your HP Nic (if any available). Also try upgrading firmware on the 1200 to the latest.

[matthew-frazier]

Hi Adam,

I'd set the preamble to long on the AP and disable aironet extensions. By default the preambe's short and the aironet extensions are on. I've seen compatibility issues with hetrogenous wireless networks when you leave these on the default.

-Matt

-Matt

[scottmac]

On the radio interface page, select the button "Default" instead of "Optimize for Throughput" or "Optimize for Distance."

Optimizing may de-select rates necesary for connection to non-Cisco NICs. This is documented in the Release Notes for the AP's IOS version.

Check it out.

Good Luck

Scott

[michaelham]

Hi Adam

I've seen this before on different hardware. It was an OQO Computer, built in wireless. What I found was when trying to connect to a WPA network the client would stay on acquiring network address. When I tried it on an open or MAC authenicated network it worked fine. There might be something in the client driver causing it, did you try updating that? Even though the laptops are new they still could have out of date drivers.

-Michael

[vramanaiah]

Did you guys, find a solution to this issue.. ?

I have the same issue.. I have upgraded the AP to different OS versions and also updated the Intel driver.

I have also set the preamble to long and disabled the aironet extensions.., but still no luck..

[scottmac]

Leave the preamble in "Auto" - "long" is for 802.11b (mostly)- "long" preambles are @ 1Mbps rate. If you also have the "b" rates disabled, you'll never connect.

Aironet extensions shouldn't matter one way or the other - they're the part of the code used for LEAP, EAP-FAST, and some other Cisco optimizations. If the client isn't asking for a CCX feature, the code is ignored.

Which Intel NIC/chipset do you have, and what version of drivers / client software are you using? MS Windows Zero Config Wireless might have a few *cough* issues. Use the Intel client software.

Good Luck

Scott