HP/Compaq w/AMD & built-in, problem with Cisco 350 and LEAP

[cole_md]

Has anybody heard of any problems using the following equipment with Cisco 350 cards and LEAP?

HP Pavilion ze4300
Compaq Presario 2100

All seem to have the AMD Athlon XP 2400+ CPU and have built-in wireless cards.

The Cisco cards appear to work if the WAPs are using static WEP keys, but will not associate if the WAP is set to use LEAP authentication.

Any suggestions as to why this is an issue? The cards were tested in other laptops without any problems, so the problem was narrowed down to these particular laptops.

[lwheeler]

Is the AP setup correctly to point to the RADIUS server, next is the RADIUS server setup correctly? Lots more going on here than meets the eye. There isn't issues for the two not to talk.
Larry

[cole_md]

Sorry if I didn't eloborate in the original post -

Yes the AP and the RADIUS server are set up correctly. Here is the scenario (and hopefully I can keep it short and still make sense!)

Branch office with a Cisco 1200 WAP using LEAP. Laptop (HP ze4300, athlon xp 2400+, win xp) using Cisco 350 pcmcia card with latest drivers, firmware, client utility. Will not associate using LEAP - times out during the authentication process (I believe its set for 180 seconds). Checking the WAP and the RADIUS server (cisco ACS server), neither show the laptop as even attempting to associate.

Placing the 350 card into another laptop (Dell) using same drivers, firmware, client utility, profile setup, etc - the Dell is able to authenticate via LEAP.

Connecting a second WAP (cisco 350) using a static WEP key (either 40 or 128 bit) - HP ze4300 is able to associate with the WAP just fine, using the same Cisco 350 pcmcia card.

Doesn't appear to be the 1200 series WAP - we can set up a second SSID with a static WEP and the HP associates fine.


The reason I assume the problem is with the HP (or the processor) is that we have had this problem in two seperate offices - both with the same model HP. We've also had a similar problem with the Compaq 2100 (same CPU), except that laptop will eventually authenticate ( unfortunately it takes almost the full 180 seconds ).

[lwheeler]

Hmm, maybe it is something that hasn't been documented yet. Did you use a wireless sniffer on it yet? See if the request is actually being transmitted and or received?
Larry

[cole_md]

Unfortunately not - can't get the approval for a decent sniffer. To make it worse, I'm dealing with it second-hand. Have knowledgable field techs working on it, but I'm not there to see the laptop in person. Might be something pre-installed from HP (I believe both laptops have built-in wireless also). I seem to recall a problem with Compaq's Homebase program (many years ago) that made problems with networking their computers. Unfortunately the laptops in question are 60+ miles away and the users aren't willing to ship them to me to work on.

Given my inability to put my hands on these, the only common point I can see is the processors and manufacturers (Athlon XP 2400+ & HP/Compaq).

[lwheeler]

Its possible, just seems unlikely, but I've seen stranger things. I'll keep my ears open.
Larry