![]() It seems to take a few moments for the service to actually stop so wait 10-15 seconds then right click NPS again and choose “Start NPS Service”. So once again on the NPS tree root right click it and select “Stop NPS Service”. Right click the NPS tree root on the left pane, and choose “Register server in Active Directory”.įinally I have noticed that NPS doesn’t seem to work after all this configuration until I’ve restarted the service. Now the NPS service needs to be activated in Active Directory. Finally enter the shared secret RADIUS key that you specified over on the router. Enter the IP address for the device, use the IP of the router interface closest to the Windows server or use the IP of the interface that you specified if you used the “ip radius” command when configuring the Cisco device. In the New RADIUS Client dialog type the friendly name that you specified earlier in the network policy for this router. Back at the Network Policy Server console in the left open up RADIUS Clients and Servers, then right click RADIUS Clients and choose New from the menu. Now we need to specify the Cisco router as a RADIUS client to the Windows NPS server. It conforms” and click Configure Attribute.įor the Vendor-assigned attribute number enter 1, for Attribute format choose String, and in Attribute value type: With Vendor set to “All”, select Vendor-Specific for the attribute and click Add.įor the attribute information select “Select from list” and choose Cisco from the menu. Under RADIUS Attributes select Vendor Specific. ![]() This next attribute setting is optional but often configured to allow users to automatically have their privileges elevated to privileged (15) EXEC mode when they login to the Cisco router. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |