Cisco validating identity error

Rated 4.29/5 based on 789 customer reviews

If a self-signed certificate (or any certificate from an untrusted CA) is in use, most clients will reject the connection since they cannot validate the server's identity.

For troubleshooting purposes, server certificate validation can be disabled on one or multiple clients, allowing those clients to connect regardless of the certificate in use.

Here are a few screenshot of this problem: This is the warning message displayed: This message says the application is BEING DOWNLOADED FROM "sub.domain.com", and that is false.

It is important to manually configure WPA2-Enterprise for your wireless network profile in Windows Vista and Windows 7. Uncheck Validate server certificate if the wireless client may not trust the RADIUS server certificate.10.

You must not be in the process of associating to the SSID because the configurations will not save correctly. If the RADIUS server has a certificate that may not be trusted by the wireless client or is not a member of the domain in which the RADIUS server resides, on the "Successfully added" page, click Change connection settings.7. For the Authentication Method, choose EAP-MSCHAP v2.11. Uncheck Automatically use my Windows logon on name and password if the computer is not on the domain.13. It may be required to specify user or computer authentication based on whether the client is part of the domain or if machine or user authentication is a condition of the RADIUS policy.

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).

Leave a Reply