<?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 timeout conn in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/timeout-conn/m-p/1344099#M825960</link>
    <description>&lt;P&gt;what would the be side of effects of setting 'timeout conn' to 5hrs?  beside the possibly of running out of connection resources. anything security related?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have a client that as a web base report that takes 5 hours to run. things where fine when the server was in-house but its now in a colo.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 16:20:16 GMT</pubDate>
    <dc:creator>deno</dc:creator>
    <dc:date>2019-03-11T16:20:16Z</dc:date>
    <item>
      <title>timeout conn</title>
      <link>https://community.cisco.com/t5/network-security/timeout-conn/m-p/1344099#M825960</link>
      <description>&lt;P&gt;what would the be side of effects of setting 'timeout conn' to 5hrs?  beside the possibly of running out of connection resources. anything security related?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have a client that as a web base report that takes 5 hours to run. things where fine when the server was in-house but its now in a colo.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:20:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/timeout-conn/m-p/1344099#M825960</guid>
      <dc:creator>deno</dc:creator>
      <dc:date>2019-03-11T16:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: timeout conn</title>
      <link>https://community.cisco.com/t5/network-security/timeout-conn/m-p/1344100#M825971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've had situations where I've had to increase the timeout conn setting to 4hrs or even 8hrs to keep telnet sessions from being dropped during the day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main issue is the possibility of something happening that opens a ton of sessions without correctly closing them.   That could lead to processor/memory usage, and eventual crash....  Although I've never seen it.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Oct 2009 04:07:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/timeout-conn/m-p/1344100#M825971</guid>
      <dc:creator>cmcbride</dc:creator>
      <dc:date>2009-10-02T04:07:54Z</dc:date>
    </item>
  </channel>
</rss>

