This one has me stumped.
We stood up radius servers in our new building, we'll call it building 2. It's pretty similar to our old building, we'll call that building 1.
- Both buildings are running Windows server 2019 VMs.
- Everything works in building 1. We have Junipers, nexus 93180s and 9336 in building 1.
- We only have 2 C93180s in building 2. The rest are Junipers and Catalyst 9500 in building 2.
- In building 2, we can putty using AD creds into everything except the C93180s. The 93180s are running 10.4(2). We are using putty v.83. I can ssh into the C93180s using local accounts. When I run "test aaa group rad-group username password, I get "User authenticated". But when I ssh using putty (or ssh from another device like a switch, firewall, or redhat box), it prompts me for a username and password. But it dies and asks me for the password again. I'll do the password 2 more times and it kills the connection. I can do that all day and my user in AD will not lock out. When I look at event viewer on the radius server, I see all of my login attempts. I have the C93180s and radius servers configured exactly like building 1. The radius debug that is created when a login attempt is made isn't clear what the issue is. I am seeing a weird error in the radius server event log: "An Access-Request message was received from RADIUS client... without a Message-Authenticator attribute when a Message-Authenticator attribute is required." Again, the configuration in the radius server and the switches are exactly the same in the two buildings.
Any thoughts?
