Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

ecoact (MIS) (OP)
18 Nov 11 2:23
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:

http://www.windowsnetworking.com/articles_tutorials/Setting-up-Wi-Fi-Authentication-Windows-Server-2008-Part2.html

and

http://andrewbevitt.com/tutorials/dd-wrt-radius-authentication-w-server-2008-r2/


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?

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close