<?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: Replacing PIX with 2811 - https problems in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/replacing-pix-with-2811-https-problems/m-p/500925#M536307</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Found the problem.  It was in the server application.  We were changing the default route to this test 2811,  but the route did not apply.  We now have it working.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Jun 2005 14:59:02 GMT</pubDate>
    <dc:creator>jcowtan</dc:creator>
    <dc:date>2005-06-24T14:59:02Z</dc:date>
    <item>
      <title>Replacing PIX with 2811 - https problems</title>
      <link>https://community.cisco.com/t5/network-security/replacing-pix-with-2811-https-problems/m-p/500923#M536300</link>
      <description>&lt;P&gt;I had set up an interim pix that supported an AS/400 HTTPS applcaition to a remote site.  No changed were made to the PIX other and setting up PPPoE.  It worked from the start!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How we are replacing the PIX with a 2811 running 12.3(8)T8.  I have attached the conifuration.  The AS/400 can no longer access the remote site and its application.   What am I missing on the 2811 to support HTTPS like the PIX did?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:13:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-pix-with-2811-https-problems/m-p/500923#M536300</guid>
      <dc:creator>jcowtan</dc:creator>
      <dc:date>2020-02-21T08:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing PIX with 2811 - https problems</title>
      <link>https://community.cisco.com/t5/network-security/replacing-pix-with-2811-https-problems/m-p/500924#M536302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need open a case in the cisco tac.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm sure that it's a BUG in inspection engine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jun 2005 06:42:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-pix-with-2811-https-problems/m-p/500924#M536302</guid>
      <dc:creator>a.alekseev</dc:creator>
      <dc:date>2005-06-24T06:42:06Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing PIX with 2811 - https problems</title>
      <link>https://community.cisco.com/t5/network-security/replacing-pix-with-2811-https-problems/m-p/500925#M536307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Found the problem.  It was in the server application.  We were changing the default route to this test 2811,  but the route did not apply.  We now have it working.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jun 2005 14:59:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/replacing-pix-with-2811-https-problems/m-p/500925#M536307</guid>
      <dc:creator>jcowtan</dc:creator>
      <dc:date>2005-06-24T14:59:02Z</dc:date>
    </item>
  </channel>
</rss>

