03-22-2011 12:13 AM
All:
I have been working on my ASA 5510 version 8.2(1) trying to change the maximum connection time. Originally the custom "Group Policy" for IPSEC (Remote Access VPN) was set to inherit the settings from the default system Group Policy (DfltGrpPolicy). The custom group policy for the sake of this discussion is called "ABCD". I have modified the settings on the default (DfltGrpPolicy) as the custom policy (ABCD) was inheriting the configuration from default to disconnect after 1200 minutes. I changed the setting "maximum connection time" to 1200 minutes. I saved the configuration and what not then connected my VPN client, after two (2) hours I was disconnected. Something just doesn't add up.
I went ahead and deselected all inherited properties and manually configured them for the ABCD custom policy. No longer was the ABCD custom policy configured to use the inherited properties/settings. I saved the configuration again tested but instead of having a 1200 minute connection limit, I have 120 minute connection limit. Inside Monitoring --> VPN --> Sesssions : I can click on my session and see Session details". The Group Policy and Connection Profile properly list the "ABCD" custom profile. However, the "Conn Time Out" setting is: 120 minutes. I am completely stumped as to what is going on.
In the actual running config I see:
group-policy abcd attributes
banner none
wins-server value 123.123.123.123
dns-server value 123.123.123.123
dhcp-network-scope none
vpn-access-hours none
vpn-simultaneous-logins 3
vpn-idle-timeout 60
vpn-session-timeout 1200
I'm stumped as to what I need to do next to get this working short of a recycle of the ASA.. Any help you can provide would be greatly appreciated.
Thanks
03-25-2011 09:55 AM
Anyone have an idea? I rebooted the ASA and still no luck. I'm stuck at the stupid connection time limit :(
04-05-2011 02:15 PM
Anyone have a clue? This time limit connection is painful to work with..
04-18-2012 08:44 AM
I know this is an old thread, but I just got done troubleshooting and issue just like this. Some had actually changed the session-timeout setting on our RADIUS server (Mircosoft IAS on Server 2003). This setting would override the vpn-session-timeout on our ASA. We banged our heads for hours on this one!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide