Wireless stuck at validating identity
By default, the IAS server checks all the certificates in the wireless client's certificate chain the series of certificates from the wireless client certificate to the root CA for revocation.
To view the EKU for a certificate in the Certificates snap-in, double-click the certificate in the contents pane, click the Details tab, and then click the Enhanced Key Usage field.
The user account has not been locked out by remote access account lockout.
Each issuing CA maintains a list of certificates that should no longer be considered valid by publishing an up-to-date certificate revocation list CRL.
Match all of the conditions of at least one remote access policy. You can use this daytime to authenticate clients when the greater does not snap CRL distribution complements, such as those from third photos.
You can use this moment to authenticate points when the event does not include CRL ace points, such as those from third tools.
When it cannot connect to a server that stores a revocation list, EAP-TLS considers the certificate to have failed the revocation check.
For Windows Server based wireless clients, use the Wireless Monitor snap-in. You must restart every domain controller in the domain in order for the change to replicate. The assumption is that the wireless client does not yet have a physical connection to the network, and therefore cannot access a Web page or other resource in order to check for certificate revocation.
This behavior can be modified with registry settings described later in this topic. To obtain the name of the remote access policy that rejected the connection attempt, ensure that IAS event logging is enabled and look for events that have IAS as the source with the Event ID set to 2.
If the CRL in a certificate is not updated often, a certificate that has been revoked can still be used and considered valid because the published CRL that the IAS server is checking is out of date. You must restart every domain controller in the domain in order for the change to replicate.
But it would seem to get continually search for, but never acquire a network address or renew the IP address.
I did all the basic stuff like updating the wireless card driver, unplugging and plugging stuff back in, right clicking and selecting Repair in Windows XP and click Diagnose and Repair in Vista.
Search for wireless stuck at validating identity:
The IAS server verifies the digital signature of each certificate in the chain, with the exception of the root CA certificate, by obtaining the public key from the certificate's issuing CA and mathematically validating the digital signature.