Aruba Radius setup

I'm trying to setup a radius server to use widows authentication  with aruba wireless devices. I'm unsure on what steps I should be taking to get this up and running.
Sean KelseyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jakob DigranesSenior ConsultantCommented:
explaning this is rather lot, really. But here's some bullet points:

- Decide if you authorize users and stations using domain username and passwords, or certificates.
- domain username and password (ms-chapv2) is the easiest, but then - users can connect "unlimited" devices with their credentials
- certificates (EAP-TLS) - the most secure, but then you need to install and configure a certificate authority and PKI infrastruture - if you haven't got one already
- You should - without any doubt - deploy Protected EAP as EAP authentication method, and then use either mschapv2 og EAP-TLS as inner method.
- With PEAP authentication, EAP-TLS (certificates) or mschapv2 (domain usernames and passwords) are exchanged within a secure channel, to avoid eavesdropping. BTW: With PEAP you need one certificate for NPS no matter what.

- Then you must decide if you want to authenticate computers, users or (best of all) both.
- if you choose both and also choose certificates, then both the computer and user needs a certificate, with usernames that is already taken care of - username and password for computer is automatic (if joined to domain).

Then Aruba
- you configures L2 authentication method of 802.1X - chooes enforce machine authentication (if you decide to authenticate machines aswell)
- You have 4 different roles with 802.1X and Aruba.
1. Logon role, not specifically for 802.1X - but this role is before you're authenticated
2. 802.1X-machine - this is the role when only computer is authenticated, before logon that is
3. 802.1X-User - this is the role when only user is authenticated. Like with a iPad (if this is set up), or if the mac-cache for the machine is expired (this is updated when logging off and on.) typically this happens if user only hibernates PC and then logs on
4. 802.1X - both machine and user is authenticated

For NPS, see here (a bit old, but still valid)

then you also need to configure client settings accordingly

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sean KelseyAuthor Commented:
Thanks, we finally got past it.  It was an IP mis-match buried deep in the settings.
Sean KelseyAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for Scott Lilly's comment #a40662331

for the following reason:

Good tips, all of which were placed in our KB vault.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Security

From novice to tech pro — start learning today.