10-12-2017 06:50 AM - edited 03-01-2019 06:11 PM
So i'm having a problem logging in to Cisco Prime using Microsoft NPS Radius authentication. I originally had it working but had to change the IP address (internet facing IP) of the Prime box and ever since it is not working, despite changing the new IP in NPS to reflect this. Everything has been setup according to various forums I have been to and all I changed was the IP to reflect the new IP of the prime box. My NPS logs are showing successfully hitting the prime box and authenticating but there must be something wrong on the prime GUI.
Thinking that there was a problem with Prime I re-created a new VM and deployed a new ova file and set this back up (as I was primarily using it to test prime) with the IP i wanted to use. I setup the radius servers again in prime using CHAP as the authentication type. However still not working. I'm completely stumped here as it was working prior to changing the IP. Has anyone any experience with Prime and Radius authentication ? / or could someone provide me with a walkthrough to what they did using prime with MS NPS ? if anyone has ideas would be grateful to hear them. Can anyone let me know where the log files are kept when users attempt to login ? Thanks
Solved! Go to Solution.
10-12-2017 07:42 AM
Think I figured it out. Looks like the shared secret on the NPS cannot be more 16 characters in length I cahnged this and seems to work ok now.
10-12-2017 07:42 AM
Think I figured it out. Looks like the shared secret on the NPS cannot be more 16 characters in length I cahnged this and seems to work ok now.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide