I am presently deploying in a Campus network of 2 WiSM's with 280 1250 AP's .
Authentication is carried by means of ACS appliance,1113. I have generated a certificate and installed on the appliance itself.
Now the problem lies, when a client tries to authenticate ,it stucks with Validating identity, but when I manually install the certificate from ACS to the client machine , it works but gives disconnection after sometime.
If Windows XP and WPA2, then you need to add the profile by hand and not with double clicking on the SSID. Then you need to change several options in the settings dialog of this connection and after that you are able to connect and authenticate.
That error mean the certificate is invalid. If you load a certificate on the client and on ACS you also have EAP-TLS enabled, then you are doing EAP-TLS authentication and not PEAP. Attach a screen shot of you ACS security setting page.
If you are using a self-signed cert then you need to either install the cert on every client you want to use PEAP on - or un-check the 'Validate server certificate' checkbox on the Windows client. Also, I uncheck 'automatically use my windows domain logon and password' this way I have to type in the username / password and I know it will be correct.
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...