Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Aironet 350 system w/ LEAP and Compaq iPAQs

I've been having a recurring, intermittant problem with DHCP-assigned IP addresses not getting assigned to Aironet 350 equipped Compaq iPAQ PDAs. I've upgraded the card (4.25.23) & AP (11.10T) firmware to the latest versions. iPAQ client software is v1.70 driver, too.

It's quite frustrating, because sometimes it works fine, then, without changing anything it will start working again.

Anyone else have similiar problems?

Regards,

Mark

7 REPLIES

Re: Aironet 350 system w/ LEAP and Compaq iPAQs

Often times complex troubleshooting issues are best addressed in an interactive session with one of our trained technical assistance engineers. While other forum users may be able to help, it’s often difficult to do so for this type of issue.

To utilize the resources at our Technical Assistance Center, please visit http://www.cisco.com/tac and to open a case with one of our TAC engineers, visit http://www.cisco.com/tac/caseopen

If anyone else in the forum has some advice, please reply to this thread.

Thank you for posting.

Community Member

Re: Aironet 350 system w/ LEAP and Compaq iPAQs

I am also experiencing the same type of issues and would be very interested in knowing the resolution.

Community Member

Re: Aironet 350 system w/ LEAP and Compaq iPAQs

I am also having this problem. I am using the client radio firmware(4.25.23) and AP (11.10T).

Community Member

Re: Aironet 350 system w/ LEAP and Compaq iPAQs

Have you loaded the Cisco Aironet Win CE client on your IPAQ? I have CE devices running in a DHCP environment with no problems.

Community Member

Re: Aironet 350 system w/ LEAP and Compaq iPAQs

Have you found a fix for this yet?

I have seen this problem also.

Community Member

Re: Aironet 350 system w/ LEAP and Compaq iPAQs

I have had very similar situation using LEAP with the same FW revs you are. Here's a couple of things to check. If your using LEAP through a CiscoSecure ACS 2.6 check the group or user settings for session limits. If the session limit count is low you're likely hitting that ceiling as I am. Users who have the session limit set to "unlimited" have no problem. Only users who use the group limit of 1 or a user limit of a few more will eventually stop being able to login and get an IP. The reason is a bug with the AP350 firmware where the NAS Port is different between "Start" and "Stop" where they should be identical. Check this by looking in ACS Reports/Radius Accounting. Look for different NAS Ports on your session Starts and Stops. Because of this if a user's account on ACS is set to allow 1 session it allows 1 successful login and DHCP assignment. Logout and then try logging back in will fail because ACS still has the "Start" NAS Port session open. After some period of time I find that session on ACS times-out and allows another successful login. The temporary workaround I have found is to set the group or users session limit to "Unlimited" until Cisco fixes the AP350 bug in one of the next rounds of firmware. Hope this helps.

Good Luck,

John

Community Member

Re: Aironet 350 system w/ LEAP and Compaq iPAQs

I had this EXACT issue! I know that someone mentioned looking at the MAX Sessios for Users, but I know that my Users and Groups in CiscoSecure ACS v2.6 were set to Unlimited.

First we tried all the latest and greatest Firmware for both the 350 Cards, and the 350 Series AP's, but the problem persisted.

We escalated to Compaq and even sent them a backup of one of our iPaq's exhibiting the problem. They finally came back and stated that they can't recreate the problem with Compaq or Lucent Wireless gear and they didn't have any Cisco gear. They then stated that we should contact Cisco.

Cisco couldn't seem to determine the problem either and wouldn't admit that there was even an acknowledged problem.

Our Fix: Updated several Compaq iPaq PPC's to PPC2002 and the problem has gone away.

So anyone that wants to wirelessly connect their iPaq's in our environment must be upgraded to PPC2002 until this problem is acknowledged at Cisco and fixed with Drivers.

238
Views
0
Helpful
7
Replies
CreatePlease to create content