Hi, this my three time that I post the same problem about authentication in VPN 3000 but until now I haven't had return on neither of the post
maybe those I'm more clear than others.
I have a VPN 3000 with PPTP Tunnel VPN and the first authentication option is on Server Radius:
Configuration > System > Server > Authentication is firstly the Server Radius and after Internal ( Authentication on Base Group Internal )
But, when I configure a user in User Management > User it isn't work. I think that authentication order is firstly Radius and if it don't find the second option is processed which ( this case ) is Internal server. but don't occour the error in log is:
Only if the radius server is actually down, or if the VPN Concentrator is not able to reach the radius server, it will then fall back to use the internal authentication.
From the error log, it seems that your radius server is rejecting the user, hence it will never fall back to use the local authentication server because it's the user that is being rejected by the radius server, ie: incorrect authentication, not inability to reach or contact the radius server.
My aim is deploy an security policy ( some users don't accesses some inside network servers) on VPN 3000 so I've thought to use the internal authentication to handle the policy. for exemplo, I wish reserve a IP address always for the same user and I'm not find how reach this with Radius authentication. with internal server is very ease.
it's possible to reserve one ip address always for the same user using Radius ?
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...