Hi Everyone,
I have configured the NPS service on my 2008 server to authenticate wireless clients using 802.11x via PEAP authentication. I have configured the network policy to use windows client authentication and allowed the Domain Users group access. I am using Linksys WRT54GL access points with DD-WRT firmware. This has been configured based on these guides:
and
I am having a problem with connecting Windows computers (Both 7 and XP) to the WPA2 Enterprise network. When the computers connect they try to authenticate as a computer rather than a user. I can specify that the computer authenticate with the domain user account in the wireless connection profile but it fails to connect. On the client computer I get an error message in the WLAN-AutoConfig event logs indicating "Failure Reason:802.1x indicated there is no authenticator, but the profile requires 802.1x.". On the server the IAS logs don't show anything at all, as if the connection is not even reaching the logs. When I allow the computer to authenticate using computer authentication the IAS logs show that it is not authenticating against the "Secure Wireless Connections" but against the "Connections to other access servers" policy which I had inadvertently enabled during setup.
I have gone through and checked all settings, deleted and recreated policies and tried every combination of settings on both client and server. The weird thing is that Mac computers can connect and authenticate against the proper policy just fine. I am at a loss, it's as if the server is not detecting that the Windows computers are attempting to wirelessly.
Any ideas?
I have configured the NPS service on my 2008 server to authenticate wireless clients using 802.11x via PEAP authentication. I have configured the network policy to use windows client authentication and allowed the Domain Users group access. I am using Linksys WRT54GL access points with DD-WRT firmware. This has been configured based on these guides:
and
I am having a problem with connecting Windows computers (Both 7 and XP) to the WPA2 Enterprise network. When the computers connect they try to authenticate as a computer rather than a user. I can specify that the computer authenticate with the domain user account in the wireless connection profile but it fails to connect. On the client computer I get an error message in the WLAN-AutoConfig event logs indicating "Failure Reason:802.1x indicated there is no authenticator, but the profile requires 802.1x.". On the server the IAS logs don't show anything at all, as if the connection is not even reaching the logs. When I allow the computer to authenticate using computer authentication the IAS logs show that it is not authenticating against the "Secure Wireless Connections" but against the "Connections to other access servers" policy which I had inadvertently enabled during setup.
I have gone through and checked all settings, deleted and recreated policies and tried every combination of settings on both client and server. The weird thing is that Mac computers can connect and authenticate against the proper policy just fine. I am at a loss, it's as if the server is not detecting that the Windows computers are attempting to wirelessly.
Any ideas?
