<?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 Pix &amp; continuous SQL/ODBC connections in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-continuous-sql-odbc-connections/m-p/40813#M687490</link>
    <description>&lt;P&gt;I've come across a problem w/ a home-grown application on a DMZ opening a connection to an internal SQL server through a PIX.  The app seems to want to open a connection and keep it open forever.  The Pix, as per default, drops the connection after an hour.  In response to irrate developers we've upped the timeout value to 3 hrs, hoping that at least some traffic would flow through that socket within that time-period.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else come across a similar problem?  Have you any other thoughts on settings that could be changed.  We'd like to limit the timeout value somewhat and are pushing the developers to write in some type of keep-alive transaction (slim chance).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 05:53:58 GMT</pubDate>
    <dc:creator>mcordiez</dc:creator>
    <dc:date>2020-02-21T05:53:58Z</dc:date>
    <item>
      <title>Pix &amp; continuous SQL/ODBC connections</title>
      <link>https://community.cisco.com/t5/network-security/pix-continuous-sql-odbc-connections/m-p/40813#M687490</link>
      <description>&lt;P&gt;I've come across a problem w/ a home-grown application on a DMZ opening a connection to an internal SQL server through a PIX.  The app seems to want to open a connection and keep it open forever.  The Pix, as per default, drops the connection after an hour.  In response to irrate developers we've upped the timeout value to 3 hrs, hoping that at least some traffic would flow through that socket within that time-period.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else come across a similar problem?  Have you any other thoughts on settings that could be changed.  We'd like to limit the timeout value somewhat and are pushing the developers to write in some type of keep-alive transaction (slim chance).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:53:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-continuous-sql-odbc-connections/m-p/40813#M687490</guid>
      <dc:creator>mcordiez</dc:creator>
      <dc:date>2020-02-21T05:53:58Z</dc:date>
    </item>
    <item>
      <title>Re: Pix &amp; continuous SQL/ODBC connections</title>
      <link>https://community.cisco.com/t5/network-security/pix-continuous-sql-odbc-connections/m-p/40814#M687507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Until you get your application fixed, you&amp;#146;ll have to keep that timeout value up there.  The only problem is, this eats away at other PIX resources.  3 hours shouldn&amp;#146;t be too bad, more might be... depending on your network and usual load.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2001 15:05:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-continuous-sql-odbc-connections/m-p/40814#M687507</guid>
      <dc:creator>smahbub</dc:creator>
      <dc:date>2001-11-15T15:05:19Z</dc:date>
    </item>
  </channel>
</rss>

