WPA2 is supported as i can connect to WPA2 personal APs. During the connection it flashes that it "connected" for a second then goes to "Validating Identity" which it eventually timesout on.
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.
unless you are running into the initial problem that most older hardware had. You may need to do a firmware upgrade on your device that is connecting to the router. Firstly you can not use WPA, you can use WPA-PSK/WPA2-PSK or WEP.
I configured the IAS policy to grant access to Domain Computers, Authentication is set to PEAP and uses a private cert issued by our CA, the other profile settings are all default.
The client settings on the laptop match the IAS settings and the certificate is definately installed.
The native SOAP API is extremely simple and is provided with a WSDL service description file.
It is also very easy to implement Open OTP One-Time Password and/or U2F functionalities into your existing Web applications.
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).
You just have to find the common setting between the two devices.
When setting up WPA you will see the option for either a radius server (Enterprise, and you see this in the corporate environment) or a place to enter a passphrase (Pre Shared Key, PSK).
The weird part is that I was using WPA TKIP with the passphrase and it was working fine.
I moved the selection tab to WPA2 only and keep the rest the same and no luck. Ok so I setup the router to only transmit wireless N and to use WPA2 only.
If you are telling me that you are using WPA with a shared key on your router, then you are using WPA - Personal. You want to make sure you are using that option on your computer. You do not want to make sure you are not using WPA-EAP. This version requires a certificate server and a matching certificate on yout computer to connect to the wireless.