cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
201942
Views
65
Helpful
17
Replies

AnyConnect Session Timeout Question

Patrick McHenry
Level 4
Level 4

We have some remote users that are not happy with the SSL Any Connect connection going down after they close their laptops or lose their wireless connection for a time. I read this question and answer from a Cisco page and was wondering where the session timeout setting is changed. Is it on the client nic, AnyConnect software or the ASA firewall?

Thanks, Pat.        

Q. What is the AnyConnect reconnect behavior?

A. AnyConnect will attempt to reconnect if the connection is disrupted. This behavior is automatic and not configurable. As long as the session on the ASA is still valid, the session will be resumed if AnyConnect can re-establish the physical connection.

Version 2.2 includes a roaming feature that allows AnyConnect to reconnect after a PC sleep. The client will continue trying indefinitely until the head-end tells it that it cannot reconnect and the client will not immediately tear down the tunnel when the system goes in to hibernate/standby. For customers who do not want this feature, set the session timeout to a low value to prevent sleep or resume reconnects.

17 Replies 17

Man, i can't even type correctly that day

it should read:

2) From system suspend- by default AnyConnect will re-authenticate,  unless you have the following configured under your AnyConnect profile:

Auto Reconnect --> Reconnect After Resume: if both settings are enabled.

---> if you don't have the "Auto Reconnect" and "Reconnect After Resume" enabled, the AnyConnect will re-authenticate. With those 2 features enable, it will resume automatically without having to re-authenticate.

I guess my statement was correct (apart from the typo)

Sir;

when the appliance desconect you for the 30 minutos inactivity , how much you have to wait to reconect again. ?? there is a value or config to config that ..

regards !!

tozmi_cokokova
Level 1
Level 1

Windows PC

Gpupdate /force

 

or

 

Netsh winsock reset

 

Should be able to resolve the issue