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.

disturbedone (Vendor) (OP)
7 Sep 11 0:37
I am new to RADIUS and have, what I thought would be, a relatively simple configuration but cannot get it to work. I suspect I know what the issue is but would like some thoughts from others.

* W2K3 domain with 2 DCs
* W2K8R2 server for NPS/RADIUS
* Followed http://www.windowsnetworking.com/articles_tutorials/Setting-up-Wi-Fi-Authentication-Windows-Server-2008-Part1.html on how to setup RADIUS but get very vague, unhelpful errors in Event log and XPSP3 laptops will not authenticate

I suspect the issue is that the W2K8R2 server is not a DC. Does it need to be a DC for authentication? If so then it's not going to work until we move to a 2K8 domain a 6mths. If not then any other suggestions?
disturbedone (Vendor) (OP)
7 Sep 11 19:22
This has been resolved. Although with all the things I was doing (removing NPS & CA roles, then adding them) I'm not 100% sure of what resolved it but I'm pretty sure it was the RADIUS secret. W2K8R2 RADIUS can generate a secret itself which was a 64 character alphanumeric (incl special characters) and it warns that some RADIUS clients may not like long secrets. The WiFi controller (the RADIUS client) allowed me to enter this and gave no warning. I changed the secret simply to "test" and it worked. The original secret only included a single "!" as a special character so I changed this to an "a" and entered the full 64 characters and it also worked so the length isn't the problem but the special character is (assuming nothing else I did was the cause).

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