Validating identity wireless
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.Does anyone know of a way to avoid having to do this?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.Not an ideal setup but your department will need to do the risk analysis.If you do go this route, make sure you document for CYA purposes.
I usually don't go to these settings as it will usually connect as long as you have the right E. I have made sure that "Enable IEEE 802.1x authentication" box unchecked in the Authentication TAB? I think there must be an issue with the router's encryption (WPA) and the USB adapter being able to connect to this encryption.
Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange 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.
In order to enable the client to connect we have to add the network manually and un-check the "Validate server certificate" as shown in the screenshot below.