CCX Verison AP1231 \ Intel Client

Unanswered Question
Apr 9th, 2009

How do I know that the Client I am using is compatible with the AP? The Intel Client is using CCX V4. We also have other clients that are at CCX V3. I am seeing some issues with Authentication using Leap wtih the Newest Intel Client.

At times the Client cannot authenticate even though there is signal. If I move to another AP I get authenticated.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
jeff.kish Thu, 04/09/2009 - 07:25

If you want to troubleshoot without CCX, you can perform the following config via CLI:

config t

interface Dot11Radio0

no dot11 extension aironet

CCX is backward-compatible, so you should have no problem running v3 and v4 clients at the same time. What version of code are you running on the AP? Maybe it's an old code that cannot support v4 clients. You could try upgrading your AP to the newest version of code and see if that helps.

ckowalchyk Thu, 04/09/2009 - 11:10

The code version is c1200-k9w7-mx.123-8.JEC. Where can you find what code version support what CCX Level? Is there a way to get this info off the AP?


Robert.N.Barrett_2 Fri, 04/10/2009 - 05:47

Can you verify that I understand the nature of the problem:

- CCX 4 client sometimes is not able to associate to a given AP (but can associate some times)

- CCX 3 clients are always able to associate to the given AP

- CC4 client will associate to another AP when not able to associate to the first AP

If the above is true:

If the CCX 4 client can associate with the given AP at least some times, then you don't have a CCX issue. You could always test this temporarily by disabling CCX support (on the AP, or on the client). If you are using the PROSet client, this is easy to do within the wireless profile.

Since the CCX 4 can associate to another AP, then what is different between the APs? Code level? Settings?

What does the given AP show for the client status when the CCX 4 client is unable to associate?

Leo Laohoo Fri, 04/10/2009 - 19:54

Hi Robert,

I get what you mean.

This made we review the post and "At times the Client cannot authenticate even though there is signal" is odd.

When this happens and before you moved to another AP, how many clients are associated to this AP? >12 or more than >25?


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