Wireless network connection stuck on validating identity

Also, since I was able to connect from my laptop with no problem, it led me to believe it was something wrong with my desktop.After about 30 minutes of fiddling around with various settings, I was able to figure out what the problem was. PEAP provides more security in authentication for 802.11 wireless local area networks that support 802.1X port access control.PEAP authentication is managed between the PEAP supplicant and the authentication server (Radius).Are you receiving an endless "Validating Identity" connection status when trying to connect to a wireless network.In a few simple steps you can bypass Windows Validation, and the resulting "Limited or No Connectivity" issue on an encrypted connection.Note:- If you do not check Validate server certificate, user credentials are not protected by the EAP server certificate.The configuration of the Microsoft PEAP (EAP-MSCHAP v2) supplicant (available in Windows XP SP1 and later and in Windows 2000 SP4)Note:- For a computer to be successfully authenticated to a domain, the computer must be registered to the domain using a non-802.1X secured network (a wired connection) prior to attempting machine authentication with PEAP.

PEAP is based on server side EAP-TLS authentication.

Select your encryption type from the "Network Authentication" and "Data Encryption" drop downs.

Uncheck "The key is provided for me automatically" and enter and confirm your Network key.

With PEAP many organizations can avoid the issues associated with installing digital certificates on every client device as required by EAP-TLS; instead, they can select the methods of client authentication, such as logon passwords or OTPs that best suit their corporate needs.

Also PEAP is an enhancement of EAP-TLS authentication, PEAP encapsulates a second-phase authentication transaction within the TLS framework.