<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hi  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807740#M160270</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think it might be database application, which might be causing connection after 5 minutes of inactivity.&lt;/P&gt;
&lt;P&gt;You can use wireshak captures on client or server to check if client or server is sending TCP-FIN or TCP-RST packet.&lt;/P&gt;
&lt;P&gt;You can use “show run all timeout” command to check timeout settings on your ASA.&lt;/P&gt;
&lt;P&gt;Default timeout for TCP connection is 60 minutes.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Jan 2016 14:11:24 GMT</pubDate>
    <dc:creator>ispatel</dc:creator>
    <dc:date>2016-01-28T14:11:24Z</dc:date>
    <item>
      <title>ASA TCP connection timeout for database</title>
      <link>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807738#M160268</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone else experienced anything similar&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:12:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807738#M160268</guid>
      <dc:creator>Mokhalil82</dc:creator>
      <dc:date>2019-03-12T07:12:24Z</dc:date>
    </item>
    <item>
      <title>What's in the ASA-Log when</title>
      <link>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807739#M160269</link>
      <description>&lt;P&gt;What's in the ASA-Log when the session dies?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 12:46:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807739#M160269</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2016-01-28T12:46:34Z</dc:date>
    </item>
    <item>
      <title>Hi </title>
      <link>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807740#M160270</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think it might be database application, which might be causing connection after 5 minutes of inactivity.&lt;/P&gt;
&lt;P&gt;You can use wireshak captures on client or server to check if client or server is sending TCP-FIN or TCP-RST packet.&lt;/P&gt;
&lt;P&gt;You can use “show run all timeout” command to check timeout settings on your ASA.&lt;/P&gt;
&lt;P&gt;Default timeout for TCP connection is 60 minutes.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 14:11:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807740#M160270</guid>
      <dc:creator>ispatel</dc:creator>
      <dc:date>2016-01-28T14:11:24Z</dc:date>
    </item>
    <item>
      <title>Thanks for the help guys</title>
      <link>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807741#M160271</link>
      <description>&lt;P&gt;Thanks for the help guys&lt;/P&gt;
&lt;P&gt;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 &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;"Oh there's a water leak, it must be the network"&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2016 07:58:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807741#M160271</guid>
      <dc:creator>Mokhalil82</dc:creator>
      <dc:date>2016-02-04T07:58:25Z</dc:date>
    </item>
    <item>
      <title>&gt; Everyone likes to blame the</title>
      <link>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807742#M160272</link>
      <description>&lt;DIV class="field field-name-comment-body field-type-text-long field-label-hidden"&gt;
&lt;DIV class="field-items"&gt;
&lt;DIV class="field-item even" property="content:encoded"&gt;
&lt;P&gt;&amp;gt; Everyone likes to blame the network in the first instance &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&amp;gt; "Oh there's a water leak, it must be the network"&lt;/P&gt;
&lt;P&gt;That's something that will never change ... &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 04 Feb 2016 15:47:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-tcp-connection-timeout-for-database/m-p/2807742#M160272</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2016-02-04T15:47:34Z</dc:date>
    </item>
  </channel>
</rss>

