Palm TX cannot connect to WLC4404 wireless network

Answered Question
Jan 21st, 2010

I work for a small junior college and am having a bit of trouble getting a Palm TX handheld unit to connect to our wireless network. I'm hoping someone will be able to help me solve this problem.


Six months ago I created a WLAN (non-broadcasting, WPA / TKIP and PSK) for three PDAs; everything was working great. Two weeks ago I upgraded the software on our wireless controller from version 4.2.112 to version 5.2.193.0 and now the PDAs cannot connect. This may be a coincidence... I dion't know. Someone suggested the possibility and it seems to make sense.


The documentation for the handhelds say they can use WEP or WPA / PSK.


I've tried connecting the PDAs with 1) no security/authentication at all, 2) WEP, and 3) WPA personal. The unit I'm testing will connect to an Apple Airport and a adhoc network on my laptop. I'm going to bring it home tonight and test it with my Netgear N-series wireless router.


I've read a little bit about a Palm TX Enterprise Security Update. The Palm unit doesn't belong to the college I work for so I can't run the update on it


This shows up in the log after I try to connect:

*Jan 21 13:54:05.250: %APF-1-CONFLICT_IN_ASS_REQ: apf_80211.c:3664 Conflicting Supported Rates in Association Request from00:0b:6c:41:3f:5

Any ideas / suggestions?


Thanks!


Lisa Coody

Weatherford College

Weatherford, TX

Correct Answer by George Stefanick about 7 years 4 weeks ago

Let experiement for a moment. Go a head and change the data rates.. 1 MEG Mandtory. Make ALL the other data rates supported.


To debug a client. CLI into the WLC that has the AP that your wireless client is attached to. The type debug client . Then turn on your wireless client and capture what it reports in the WLC.


Your feedback: *Jan 21 13:54:05.250: %APF-1-CONFLICT_IN_ASS_REQ: apf_80211.c:3664 Conflicting Supported Rates in Association Request from00:0b:6c:41:3f:5


Conflicting supported rates is the intesrting peice. When you SAY make a RATE MANDATORY. A client MUST support that rate, and if it doesnt she will not likly connect . So lets give this a spin...

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
George Stefanick Fri, 01/22/2010 - 23:29

oh ...  Conflicting Supported Rates in Association Request from00:0b:6c:41:3f:5... this is a good place to start ...



What is your controller date rates set at



go to WIRELESS--> 802.11 b/g/n--> Network then post your data rate settings


EXAMPLE



Data Rates**
1 Mbps                     Supported                     Mandatory                     Disabled                    
2 Mbps                     Supported                     Mandatory                     Disabled                    
5.5 Mbps                     Supported                     Mandatory                     Disabled                    
6 Mbps                           Supported                        Mandatory                        Disabled                        
9 Mbps                     Supported                     Mandatory                     Disabled                        
11 Mbps                     Supported                     Mandatory                     Disabled                    
12 Mbps                           Supported                           Mandatory                           Disabled                        
18 Mbps                         Supported                         Mandatory                         Disabled                        
24 Mbps                           Supported                           Mandatory                           Disabled                        
36 Mbps                          Supported                          Mandatory                          Disabled                        
48 Mbps                     Supported                     Mandatory                     Disabled                        
54 Mbps                     Supported                     Mandatory                     Disabled                        




Also do a debug of the client in the CLI .. and post your results

lisacoody Tue, 01/26/2010 - 07:28

George,


Thanks for your reply. Here's what is shown under Wireless > 802.11b/g/n  > Network


1Mbps     Mandatory

2Mbps     Mandatory

5.5Mbps  Mandatory

6Mbps     Mandatory

9Mbps     Mandatory

11Mbps   Supported

12Mbps   Disabled

18Mbps   Disabled

24Mbps   Disabled

36Mbps   Disabled

48Mbps   Disabled

54Mbps   Disabled


I'm sorry, but I don't know how to do a debug of the client in the CLI. I'm still pretty new to this system. I'll try to figure it out and post that information also. Thank you very much for your help.


Lisa


P. S. I tried to do a copy / paste of the Data Rates, but all rates showed up as "supported" in my reply even though they show differently in my WLC page. I just decided to manually enter the data rates and if they are supported / disabled / mandatory.

Correct Answer
George Stefanick Tue, 01/26/2010 - 09:40

Let experiement for a moment. Go a head and change the data rates.. 1 MEG Mandtory. Make ALL the other data rates supported.


To debug a client. CLI into the WLC that has the AP that your wireless client is attached to. The type debug client . Then turn on your wireless client and capture what it reports in the WLC.


Your feedback: *Jan 21 13:54:05.250: %APF-1-CONFLICT_IN_ASS_REQ: apf_80211.c:3664 Conflicting Supported Rates in Association Request from00:0b:6c:41:3f:5


Conflicting supported rates is the intesrting peice. When you SAY make a RATE MANDATORY. A client MUST support that rate, and if it doesnt she will not likly connect . So lets give this a spin...

lisacoody Tue, 01/26/2010 - 10:01

George,


I have 185 clients connected right now. If I change the data rates will those users be disconnected? I can't do anything to disrupt service right now.


I did a 'debug client' command and tried to connect. The results are below:


(Cisco Controller) >debug client ?

     MAC address

(Cisco Controller) >debug client 00:0b:6c:41:3f:55

(Cisco Controller) >*Jan 26 11:53:20.559: 00:0b:6c:41:3f:55 Adding mobile on LWAPP AP 00:22:55:0c:29:c0(0)
*Jan 26 11:53:20.559: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 23) in 5 seconds
*Jan 26 11:53:20.559: 00:0b:6c:41:3f:55 apfProcessProbeReq (apf_80211.c:4598) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Probe

*Jan 26 11:53:20.559: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:20.559: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:20.572: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:20.997: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3b:30
*Jan 26 11:53:20.997: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:20.997: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3b:30 (status 18)
*Jan 26 11:53:20.997: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 22) in 3 seconds
*Jan 26 11:53:22.015: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:22.428: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:22.428: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Probe to Idle

*Jan 26 11:53:22.428: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5428) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:22.428: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 28) in 10 seconds
*Jan 26 11:53:23.871: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3b:30
*Jan 26 11:53:23.871: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:23.871: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3b:30 (status 18)
*Jan 26 11:53:23.871: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 22) in 3 seconds
*Jan 26 11:53:25.295: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:25.295: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:25.295: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5428) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:25.295: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 28) in 10 seconds
*Jan 26 11:53:26.731: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3b:30
*Jan 26 11:53:26.731: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:26.731: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3b:30 (status 18)
*Jan 26 11:53:26.731: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 22) in 3 seconds
*Jan 26 11:53:28.165: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:28.165: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:28.165: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5428) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:28.165: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 28) in 10 seconds
*Jan 26 11:53:29.612: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3b:30
*Jan 26 11:53:29.613: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:29.613: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3b:30 (status 18)
*Jan 26 11:53:29.613: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 22) in 3 seconds
*Jan 26 11:53:31.030: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:31.030: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:31.030: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5428) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:31.030: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 28) in 10 seconds
*Jan 26 11:53:32.465: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3b:30
*Jan 26 11:53:32.465: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:32.465: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3b:30 (status 18)
*Jan 26 11:53:32.465: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 22) in 3 seconds
*Jan 26 11:53:33.897: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:33.897: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:33.897: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5428) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:33.897: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 28) in 10 seconds
*Jan 26 11:53:35.333: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3b:30
*Jan 26 11:53:35.333: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:35.333: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3b:30 (status 18)
*Jan 26 11:53:36.764: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:36.764: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:38.202: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3b:30
*Jan 26 11:53:38.202: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:38.202: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3b:30 (status 18)
*Jan 26 11:53:39.637: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:39.637: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:41.039: 00:0b:6c:41:3f:55 Association received from mobile on AP 00:22:55:0c:3d:d0
*Jan 26 11:53:41.039: 00:0b:6c:41:3f:55 STA - rates (4): 130 132 11 22 0 0 0 0 0 0 0 0 0 0 0 0
*Jan 26 11:53:41.039: 00:0b:6c:41:3f:55 Sending Assoc Response to station on BSSID 00:22:55:0c:3d:d0 (status 18)
*Jan 26 11:53:42.396: 00:0b:6c:41:3f:55 Received Auth Request from station on AP 00:22:55:0c:3b:30 (vapId 7)
*Jan 26 11:53:42.396: 00:0b:6c:41:3f:55 apfProcessAuthReq (apf_80211.c:5204) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:29:c0 from Idle to Idle

*Jan 26 11:53:43.349: 00:0b:6c:41:3f:55 apfMsExpireCallback (apf_ms.c:417) Expiring Mobile!
*Jan 26 11:53:43.350: 00:0b:6c:41:3f:55 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [00:22:55:0c:29:c0]
*Jan 26 11:53:43.350: 00:0b:6c:41:3f:55 Deleting mobile on AP 00:22:55:0c:29:c0(0)
*Jan 26 11:53:52.837: 00:0b:6c:41:3f:55 Adding mobile on LWAPP AP 00:22:55:0c:3b:30(0)
*Jan 26 11:53:52.837: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 23) in 5 seconds
*Jan 26 11:53:52.837: 00:0b:6c:41:3f:55 apfProcessProbeReq (apf_80211.c:4598) Changing state for mobile 00:0b:6c:41:3f:55 on AP 00:22:55:0c:3b:30 from Idle to Probe

*Jan 26 11:53:52.837: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:52.837: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:52.837: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:52.951: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.300: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.300: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.300: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.443: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.443: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.443: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.443: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:53.455: 00:0b:6c:41:3f:55 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
*Jan 26 11:53:58.056: 00:0b:6c:41:3f:55 apfMsExpireCallback (apf_ms.c:417) Expiring Mobile!
*Jan 26 11:53:58.056: 00:0b:6c:41:3f:55 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [00:22:55:0c:3b:30]



Thanks for your help!

George Stefanick Tue, 01/26/2010 - 11:32

Yes, they may go blip for a second. Do you have a standby controller you can move an AP over to for testing?

lisacoody Tue, 01/26/2010 - 11:38

Unfortunately this is our only controller - well, actually I have another, but it is not set up yet. That's another project.


I'll wait until later today when there aren't so many users online - I have 200 connected now. I'll change the data rates and if I still can't get the PDA to connect I'll do a 'debug client' command again and post the results.


Thank you SO much for your assistance.


Lisa

George Stefanick Tue, 01/26/2010 - 12:01

ok, no problem. if you have a sniffer like AirMagnet or Omnipeek this could also aid in your troubleshooting. If you apply a filter and look only at your clients MAC tarffic you can see the 802.11 frame transactions. In most cases this information is very telling ... I would also test with an unsecured ssid, so if you havent already; create an open SSID and configure your device as unsecure as well.

lisacoody Wed, 01/27/2010 - 06:07

George,


Changing the data rates fixed the problem. As soon as I set 1Mbps as "mandatory" and the rest "supported" the PDA connected immediately.


Thank you very much for your assistance!


Lisa

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode