Cisco Wireless Client Association

Unanswered Question
Oct 4th, 2009
User Badges:

I have a 2106 WLC and a 1131AG access point. I have a wireless client that is not associating to the AP. It can see the wireless SSID but when I associate it fails.

When I am debugging on the WLC it shows the text below. I have been doing some reseach on debugging and I found this cisco article

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a008091b08b.shtml

In the article I found something that appears very close to my debug messages shown below also. I am sure I have the client set to wpa2 psk and the wlan ssid set to wpa2 psk. I am sure the psk also match. It referances "some parameters not supported". What can those be?


I am able to associate with other clients and everything is fine. I tried removing all security and leaving the SSID open instead of wpav2 and I still get the same debug and not able to associate so I have a feeling maybe it's some parameter that's not jiving with cisco wireless? Any ideas would be welcomed



Attachment: 
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Leo Laohoo Sun, 10/04/2009 - 15:08
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

What is the brand or model of the wireless NIC card?


Try going to the manufacturer's website and verify if the firmware for the wireless NIC card is up-to-date.

JASON BOYERS Sun, 10/04/2009 - 17:41
User Badges:

If both the SSID and your client were configured for open, and you still couldn't associate, something doesn't jive. There are a couple of things that can cause an issue like this.


1) Is the MFP Client Protection "Required" under the advanced tab?

2) Is the WMM Policy "Required" under the QoS tab?

3) Is the "Aironet IE" enabled under the advanced tab of the SSID? That can cause problems for some clients.


Any of those (especially the first two) would cause a similar issue with not being able to associate, as having mismatched encryption types.

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