I'm having a weird issue with two devices when I'm trying to use Radius for login authentication.
I get the following log messages.
%RADIUS-4-RADIUS_DEAD: RADIUS server 10.1.1.20:1645,1646 is not responding.
Jun 17 09:01:34.256: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.1.1.20:1645,1646 has returned.
Jun 17 09:01:53.810: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.1.1.23:1645,1646 is not responding.
There will occasionaly be these entries in the log. I can also "force" these messages to be generated by trying to login with Radius.
I know the Radius server is available. It runs on our primary domain controller via IAS and is used for all of our RAS and Wireless authentication. In this particular case, the IAS server is 1 switch hop away. I've checked the uplink ports on the switch and they're clean of errors, same duplex / speed on both sides. The IAS logs show a successful authentication, but the switch says it timed out.
I've done some forum-digging and people have referred to this same problem and said that an IOS upgrade has fixed the problem, Is this an IOS bug or what's the deal?
I have two devices in particular this is occuring on:
Located in my datacenter, 1 switch hop from server
Located across the WAN. WAN links are clean and free of errors. Same scenario.
Any thoughts as to why this is happening? Will an IOS upgrade really fix my problems?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...