We are perfectly willing to buy a certificate from Verisign, Thwarte, etc if it will help but have tried our Comodo wildcard SSL certificate which hasn't fixed it.These machines belong to the end users so we can't easily control settings with group policy or registry hacks.
This is the approach I used and some lessons learned: First, I used multiple SSIDs to provide the primary network on WPA2-Enterprise, and an open network for user enrollment.
The open network redirects to a custom captive portal (using HTTPS and a normal certificate issued by a CA) where users signed up and provided payment information.
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.
This week when I get in, I notice that my phone can not connect to the wireless.
This article will help you fix the validation and certificate errors in Windows XP and Vista, every time you connect to your NETGEAR router.
Symptoms: After entering the correct network or passphrase for a wireless connection, you see one of the following: To avoid these error messages, you need to manually create or add a wireless network profile.
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.
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.
You need to distribute your RADIUS server's certificate (if it was self-signed) or the certificate of the Certificate Authority that signed it to your clients.