Layer 2/3 switching: Trouble Implementing RADIUS via Windows NPS to authenticate login

[james_schena]

Looking for the SME out there that has the information regarding implementing Windows NPS as a small to medium scale version of RADIUS authentication. I have found snips here and there of pieces of the puzzle but they don't seem to be coming together correctly to properly authenticate. This is what I have so far:

-NPS Service is started and registered with AD

-RADIUS client is added with "friendly Name" and IP

-Switch has the following aaa commands:

aaa authentication enable default radius enable
aaa authentication login default radius local
aaa authentication login privilege-mode
aaa authorization exec default radius
aaa accounting commands 0 default start-stop radius

radius-server x.x.x.x

radius-server key test

I have tried several Network policies and configurations that I found online, but nothing seems to be the key to the castle.

I am currently getting access denied statements from the switch and NPS logs are saying an unauthorized IP  is attempting to access the NPS with code 13 listed.

Any assistance is appreciated.