HTC mobile phone access WLAN problem

Configuring Wireless Cisco Networks and Wireless Controllers.
Guest

HTC mobile phone access WLAN problem

Post by Guest » Wed Jul 22, 2009 3:16 pm

Hi, We have Cisco LAP wireless environment, The WLC is WiSM software version is 7.0.98.0 , access point is Cisco 1142. We have one user with HTC mobile phone ( OS is Android 2.2 ) can not access to WLAN ( WEP key + WEB authentication ), it must take long time to get IP address or can not get IP address. Is there someone have similar problem? Best Regards, Jackson Ku

Guest

Re:HTC mobile phone access WLAN problem

Post by Guest » Wed Jul 22, 2009 3:30 pm

seems like a WEP key mismatch...can any other device connect to the SSID and get an IP address?

Guest

Re:HTC mobile phone access WLAN problem

Post by Guest » Wed Jul 22, 2009 3:43 pm

Hi, The WEP key is correct, the laptop can connect this WLAN. Best Regards, Jackson Ku

Guest

Re:HTC mobile phone access WLAN problem

Post by Guest » Wed Jul 22, 2009 4:12 pm

run some debugs from the WLC... What is the size of the web key? debug client xx:xx:xx:xx:xx:

Guest

Re:HTC mobile phone access WLAN problem

Post by Guest » Wed Jul 22, 2009 4:25 pm

Hi, The debug log are A/F : *apfMsConnTask_0: Apr 21 11:11:26.600: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0) *apfMsConnTask_0: Apr 21 11:11:26.600: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40*apfMsConnTask_0: Apr 21 11:11:26.601: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile *apfMsConnTask_0: Apr 21 11:11:26.601: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)*osapiBsnTimer: Apr 21 11:11:31.434: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!*apfReceiveTask: Apr 21 11:11:31.434: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40]*apfReceiveTask: Apr 21 11:11:31.434: 40:fc:89:30:3a:dd Deleting mobile on AP c0:62:6b:29:9d:40(0) *apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0) *apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40*apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile *apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)*osapiBsnTimer: Apr 21 11:11:54.234: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!*apfReceiveTask: Apr 21 11:11:54.234: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40]*apfReceiveTask: Apr 21 11:11:54.234: 40:fc:89:30:3a:dd Deleting mobile on AP c0:62:6b:29:9d:40(0) *apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0) *apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40*apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile *apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)*osapiBsnTimer: Apr 21 11:12:17.834: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!*apfReceiveTask: Apr 21 11:12:17.834: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40] Best Regards, Jackson Ku

Post Reply