Validating identity cisco
WPA2 is supported as i can connect to WPA2 personal APs. During the connection it flashes that it "connected" for a second then goes to "Validating Identity" which it eventually timesout on.I am using the Windows Wireless Connection Manager. On a couple of occasions I've seen that particular AP (don't know what firmware) suddenly stop attempting to authnenticate clients (it never sends any RADIUS requests) and power-cycling the AP "fixes" the issue.I suspect a firmware upgrade probably fixes that behaviour. If you want to accept both computer credentials and user credentials you'll need to name both "Domain Comptuers" and "Domain Users" in your policy.By default, XP will re-authenticate with the user credential after the user logs-on (there is no way to do computer-only with XP, I believe).You must configure the external identity source that contains your user information in Cisco ISE.External identity sources also include certificate information for the Cisco ISE server and certificate authentication profiles.
If using OS X, sometimes it can take up to 10 seconds for authentication to complete.
I recenty switched from AT&T Uverse to Time Warner because AT&T Uverse could not support Cisco VPN Client.
The family all use MACs but I have a PC because my job requires a computer with windows.
When Windows XP or 7 clients connect they initally fail to connect.
In order to enable the client to connect we have to add the network manually and un-check the "Validate server certificate" as shown in the screenshot below.
This is accomplished by hosting a certificate on the RADIUS server that has been validated by a trusted Certificate Authority (CA).