Windows xp peap validating identity

Rated 3.99/5 based on 675 customer reviews

Ok so I setup the router to only transmit wireless N and to use WPA2 only.

When I try to connect using the windows zero configuration utility it gets stuck validating identity.

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.

I moved the selection tab to WPA2 only and keep the rest the same and no luck.

Then my Windows 10 laptop could not connect (both have connected before).

Only clients that have not disconnect from the network were still able to access it.

I know this post is really old, however, this is similar to my issue except that last week, any client could connect to my wireless network and this week they can not. The windows/android/iphone clients were able to connect with 802.1x verifying against a local, Aruba based database of one user name.

In turn the signing certificate authority's public key will be distributed to clients, either through GPOs, Active Directory Certificate Services or it was included by Microsoft in the Trusted Root Certification Authority repository.

It's not a recommended configuration to have a external root CA sign your RADIUS server's certificate.

This is from the Free RADIUS documentation but I expect it is equal valid for the Microsoft implementation: In general, you should use self-signed certificates for 802.1x (EAP) authentication.

We're deploying a wireless networking using Windows Server 2008 NAC as a RADIUS server.

When Windows XP or 7 clients connect they initally fail to connect.

Leave a Reply