(RADIATOR) Cisco VPN client not authenticating?

[Hugh Irvine]

Hello Steve -

It does sound like the firewall is not configured properly - one of:  
radius authentication not enabled, target IP address and/or target  
UDP port number incorrect.

As you say, if you don't see anything in the Radiator log, there  
isn't much that Radiator can do.

As usual to say any more I will need to see a copy of your  
configuration file and a trace 4 debug showing what is happening.

regards

Hugh



On 13 Mar 2007, at 03:10, Steve Hahn wrote:

> I’ve configured my Cisco firewall (ASA 5510, accessed via ASDM 5.2)  
> to authenticate VPN users to my Radiator server, and I know I’ve  
> done this correctly since when I’m in ASDM I can send a test  
> authentication to the Radiator server and it works wonderfully. But  
> when I configure the Cisco VPN client to log in this way instead of  
> through a shared secret, it fails; I don’t think the firewall is  
> even sending the authentication info to Radius, since it doesn’t  
> log anything when I try to connect.



NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/ 
radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.



--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.