ASA TCP connection timeout for database
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2016 04:16 AM - edited 03-12-2019 12:12 AM
Hi
I have a new database which is access via the firewall. After 5 minutes of inactivity it times outs. I am wondering whether this is due to the TCP connection timing out although I have not configured anything on the firewall to timeout the connections. I do have other databases accessed via the firewall and this does not affect any others.
Has anyone else experienced anything similar
- Labels:
-
NGFW Firewalls
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2016 04:46 AM
What's in the ASA-Log when the session dies?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2016 11:58 PM
Thanks for the help guys
It turned out it was a local database setting causing the connection to timeout. After doing packet traces I found the traffic did not even hit the firewall. Its a funny network setup. Everyone likes to blame the network in the first instance :-)
"Oh there's a water leak, it must be the network"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2016 07:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2016 06:11 AM
Hi
I think it might be database application, which might be causing connection after 5 minutes of inactivity.
You can use wireshak captures on client or server to check if client or server is sending TCP-FIN or TCP-RST packet.
You can use “show run all timeout” command to check timeout settings on your ASA.
Default timeout for TCP connection is 60 minutes.

> Everyone likes to blame the network in the first instance :-)
> "Oh there's a water leak, it must be the network"
That's something that will never change ... ;-)