01-20-2022 06:55 PM
RADIUS ACCT Server 192.168.40.58:1813 deactivated in global list
RADIUS server 192.168.40.58:1812 failed to respond to request (ID 41) for client 56:61:55:3e:c2:e5 / user 'ThePlague'
I keep getting these errors when I am trying test test 802.1X I checked the firewall in the auth and accounting server and made a rule to allow inbound connections on port 1812-1813 i tried turning off the firewall and i checked my main firewall and there are no rules blocking it I dont know why i am getting it i double checked the secret and the ip addresses
01-20-2022 07:01 PM
what radius server ACS / ISE? check is the WLC IP is added in NAD list with a secret?
what Logs do you see on the Radius side?
check some config examples:
01-20-2022 07:13 PM
Im using Windows Server NPS
01-20-2022 07:17 PM
check on the Windows NPS Logs.
01-20-2022 07:20 PM
They dont show up it is not making logs
01-20-2022 10:06 PM
If you don’t see logs, then the traffic is not reaching to NPS server. Make sure that the Windows FW is not blocking that traffic also.
A few questions, is this a new setup? Is this working for any other services? Have you tried to restart the NPS service or the box itself? From the NPS server, run a telnet to the controller ip using port 1812 and 1813 or from another device on the same subnet as the controller.
01-20-2022 11:47 PM
Another thing that could be making NPS not to log anything is a mismatch in the Shared Secret between WLC (or APs if you're using local atuh from Flexconnect APs) and NPS server.
HTH
-Jesus
*** Please rate helpful responses ***
01-21-2022 12:00 AM
Then you need other methods to get the information what is failing, Wireshark ?
01-21-2022 05:04 AM
I figured it out I dont know what i did though
01-21-2022 05:23 AM
glad end it all working that is important, good if you documented the steps, in case if it occur again to fix the issue and share with community. since all working we mark as resolved now.
01-21-2022 07:16 PM
The Funny thing is i have no idea what i did that fixed it I was just doing changes and it started working that is the best fix right ahahahaha
01-22-2022 08:55 AM
A fix is a fix, but sometimes it's best to keep track of your changes, because usually it will happen again in the future.
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