I cannot get WPA2 enterprise to work on my network. Windows Domain, using IAS and its own CA Linksys WAP200 Access Point I setup the AP to use WPA2-Enterprise Mixed using RADIUS I setup and registered IAS on the domain controller.I added the AP as a client with and have tried using both RADIUS Standard and Cisco as the RADIUS type.In a few simple steps you can bypass Windows Validation, and the resulting "Limited or No Connectivity" issue on an encrypted connection.In the next window click on the "Authentication" tab, Make sure "Enable IEEE 802.1x...." checkbox is UN-Checked, the rest of this window should be greyed out.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).This article also describes the most common problems with IAS authentication and authorization, certificate properties, and the process of certificate validation for both wireless client and IAS server certificates.This article assumes background knowledge in IEEE 802.11 wireless LAN and associated security technologies and the components of a Windows-based authentication infrastructure.
The Network Connections folder and the notification area icons provide information about the state of the authentication.
Uncheck "The key is provided for me automatically" and enter and confirm your Network key.
To fix, you go into the properties page of your wireless connection, go to "Wireless Networks" tab and then to Properties of the chosen wireless network you are trying to connect to.
For background information, see Wireless LAN Technologies and Microsoft Windows.
For detailed information about a Windows-based authentication infrastructure, see Wireless Deployment Technology and Component Overview.