No, those timeouts don't apply to VPN users. I'd recommend enabling logging on the client software for one or more of the users who are having the problem since the client log tends to be more informative than the corresponding logs in the ASA, and they only apply to that client so you don't have to wade through a bunch of messages that aren't pertinent. Set all the levels to 3, the highest setting, and have the user save the log messages to a file and send them to you when they see the problem. I suspect you'll see messages akin to "remote peer not responding", which points to some sort of connectivity problem between them and the ASA. Otherwise, these users could also be seeing an issue with the forced keepalives. The first question in this article at Cisco's web site talks about this and tells how to turn them off by editing the client .pcf file:
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...