I am not going to re-invent the wheel here. See these two blogs for info on initial setup on the PowerConnect and Radius server.
Both of these links do a great job explaining what you need to do on the PowerConnect and the Server. Make sure you at least do the following:
Setup Local Admin
Setup Radius List
Setup Radius servers – Two servers seemed to work however vNetWise mentioned issues in their implementation
Configure Telnet, SSH, HTTP(s)
Configure Radius Clients on Windows Server
Create NPS Network Policy
There are two things that are not mentioned or only mentioned by visitors in the comments.
First, there is a 48 character limit for the Radius key. If the standard 64 characters generated by the server are used, you will get Event 6273, Error 16 “Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.”
Second, you have to setup a connection request policy or the Network Policy Server will refuse the connections with Event 6273, Error 49 “The RADIUS request did not match any configured connection request policy (CRP).”
These are the settings I used to create a our connection request policy:
After both of these changes were implemented, we were able to successfully authenticate with radius.
Hopefully these steps help you in your quest to use radius authenticate on your Dell PowerConnect Switch!
Remember, tips are always appreciated – BTC 17QJoiG7uWvumPjpvECXZgi5GqSPUbYf21