Answered by:
NPS Event ID 13 and Event ID 10

Question
-
This past monday I had an entire department that couldn't log in. Looking at the event log I see hundreds of Event ID 13 messages:
A RADIUS message was received from the invalid RADIUS client IP address x.x.x.x
(I removed the IP for security reasons)
The IP was of a valid switch. Prior to the Event 13, I get an Event 10:
The name, <SWITCHNAME>, of the RADIUS client, <SWITCHNAME>, could not be resolved. The data is the error code generated by Windows Sockets.
-GunnarSo it looks to me like name resolution failed in the morning and that in turn is why the Event 13 occured becuase NPS didn't know who the IPs were. I have since changed my RADIUS clients to IP instead of name, but I'd really like to know what caused this. My DNS servers did not fail on Monday.
Answers
-
Hi, Gunnarwb
About Event 13, you can refer to http://technet.microsoft.com/en-us/library/dd316135(WS.10).aspx.
there article has the information about the different reasons and solutions.
Regards
Qunshu
Sorry. My posting is my personal suggestion, Microsoft won't take any responsibilities for my posting. But I am more than happy to try my best to help you.- Marked as answer by Greg LindsayMicrosoft employee, Owner Tuesday, December 15, 2009 12:13 AM
-
I would make sure you DO NOT use the DNS name of the switch as a RADIUS client but instead use the IP Address....
- Marked as answer by Greg LindsayMicrosoft employee, Owner Tuesday, December 15, 2009 12:14 AM
All replies
-
Hi, Gunnarwb
About Event 13, you can refer to http://technet.microsoft.com/en-us/library/dd316135(WS.10).aspx.
there article has the information about the different reasons and solutions.
Regards
Qunshu
Sorry. My posting is my personal suggestion, Microsoft won't take any responsibilities for my posting. But I am more than happy to try my best to help you.- Marked as answer by Greg LindsayMicrosoft employee, Owner Tuesday, December 15, 2009 12:13 AM
-
I would make sure you DO NOT use the DNS name of the switch as a RADIUS client but instead use the IP Address....
- Marked as answer by Greg LindsayMicrosoft employee, Owner Tuesday, December 15, 2009 12:14 AM