<?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 Re: ASA timeouts in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-timeouts/m-p/838352#M973570</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So if you mean you have configured a PIX/ASA for  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"timeout conn 24:00:00"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then an idle TCP connection will timeout after 24 hours.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first thing i would ask is if that this connection in reality, is idle for 24 hours. If it is.. is it a well known port? Some applications have their own timeout value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie "timeout rpc", "timeout udp"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Oct 2007 16:54:21 GMT</pubDate>
    <dc:creator>nathancielieska</dc:creator>
    <dc:date>2007-10-16T16:54:21Z</dc:date>
    <item>
      <title>ASA timeouts</title>
      <link>https://community.cisco.com/t5/network-security/asa-timeouts/m-p/838351#M973569</link>
      <description>&lt;P&gt;Hi; &lt;/P&gt;&lt;P&gt;I configured a timeout in the 6506 for "Connections" of "24:00:00". &lt;/P&gt;&lt;P&gt;Is the only one configured. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I connect a machine from the outside to the inside and it doesn't close the connection (know stablisehd for 4 days). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if I dissable the "connection" timeout, the same connection (outside--&amp;gt; inside) is closed in one hour. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need the connection for several hours, but no permanently. &lt;/P&gt;&lt;P&gt;How I can do it? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks. Regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:25:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-timeouts/m-p/838351#M973569</guid>
      <dc:creator>ehuarte</dc:creator>
      <dc:date>2019-03-11T11:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: ASA timeouts</title>
      <link>https://community.cisco.com/t5/network-security/asa-timeouts/m-p/838352#M973570</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So if you mean you have configured a PIX/ASA for  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"timeout conn 24:00:00"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then an idle TCP connection will timeout after 24 hours.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first thing i would ask is if that this connection in reality, is idle for 24 hours. If it is.. is it a well known port? Some applications have their own timeout value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie "timeout rpc", "timeout udp"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Oct 2007 16:54:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-timeouts/m-p/838352#M973570</guid>
      <dc:creator>nathancielieska</dc:creator>
      <dc:date>2007-10-16T16:54:21Z</dc:date>
    </item>
  </channel>
</rss>

