But according to new research, routers with WPS are vulnerable to a very basic hacking technique: The brute-force attack.Put simply, an attacker can try thousands of combinations in rapid succession until he happens on the correct 8-digit PIN that allows authentication to the device.If the box was checked, then that was why you were getting the “unable to find a certificate to log you on to the network” message because Windows is looking for one, but your wireless router is not setup for certificate security. Once I unchecked that box and tried to reconnect to the wireless network, everything worked fine! Security researchers have released new tools that can bypass the encryption used to protect many types of wireless routers.
Select Properties once you locate the wireless network causing the error.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).I'd start by reviewing the event logs on your IAS server for reasoning as to why it's not authenticating your client.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.