We are seeing more and more clients having issues connecting to the internal wireless network. Recently my computer has become a victim of this too. When trying to connect, the windows client just hangs at "Validating Identity." I originally thought it was a density issue as when I added AP's to certain areas, it seemed to fix the issue. There are some areas; however, that only have 5 clients and the issue is still prevalent. I did notice consistency in one building where the people who could not connect had new Dell 6400 laptops and they were trying to connect to 1231 AP's - the new 1242 fixed their issue.
I am using a Dell Latitude D630 and I am trying to connect to a lightweight 1242. I set up netsh on my laptop, please see the attachment with the results.
Please let me know what you think. This is becoming a large-scale issue.
What EAP method are you using? Are you seeing messages on your RADIUS server to indicate delays or retries? If you are using PEAP or EAP-TLS, have you set the clients to validate the server certificate when they shouldn't (because they don't trust the RADIUS server certificate)?
Since it appears you are using WZC with XP, make sure you are running XP SP2 with the wireless update, or XP SP3. However, could a difference between your clients be SP2 versus SP3?
We are using PEAP to authenticate and my machine has SP3 installed. It doesn't seem consistent with service packs since some of the people with problems have SP2 installed.
I recently set up an autonomous access point with all the same settings as our lightweight AP's - minus the controller of course and I was able to connect. This leads me to believe that there is something in the controller that is excluding certain clients. I have checked WCS for excluded clients and I do not see these clients.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...