<?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: Configuring PIX 525 - client behind Pix using SecureRemote in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/configuring-pix-525-client-behind-pix-using-secureremote/m-p/67588#M620359</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, PAT is the problem.  PAT and IPSec don't work well together, since PAT uses the TCP/UDP port number to differentiate between sessions, and IPSec is not a TCP/UDP protocol (it sits right on top of IP).  The connection is established successfully because that is done with ISAKMP, which is a UDP protocol, so that can be PAT'd OK.  The data is sent in IPSec packets, which can't be PAT'd.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You'll have to create a static one-to-one translation for the client and then it'll work fine.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, in PIX 6.3 code (not released yet), there is supposed to be support for IPSec thru PAT (IPSec passthru), so watch out for it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Jul 2002 02:19:36 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2002-07-17T02:19:36Z</dc:date>
    <item>
      <title>Configuring PIX 525 - client behind Pix using SecureRemote</title>
      <link>https://community.cisco.com/t5/network-security/configuring-pix-525-client-behind-pix-using-secureremote/m-p/67587#M620358</link>
      <description>&lt;P&gt;The Pix is using global PAT. IPsec-permit has been enabled. Ver 5.2.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client is in the dmz. When he iniates the connection he gets authenticated but no traffic will pass, ie. can't ping or use terminal services.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outside the pix the client  works. Is the use of PAT the problem? What is the solution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:09:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/configuring-pix-525-client-behind-pix-using-secureremote/m-p/67587#M620358</guid>
      <dc:creator>pbunchuk</dc:creator>
      <dc:date>2020-02-21T06:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring PIX 525 - client behind Pix using SecureRemote</title>
      <link>https://community.cisco.com/t5/network-security/configuring-pix-525-client-behind-pix-using-secureremote/m-p/67588#M620359</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, PAT is the problem.  PAT and IPSec don't work well together, since PAT uses the TCP/UDP port number to differentiate between sessions, and IPSec is not a TCP/UDP protocol (it sits right on top of IP).  The connection is established successfully because that is done with ISAKMP, which is a UDP protocol, so that can be PAT'd OK.  The data is sent in IPSec packets, which can't be PAT'd.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You'll have to create a static one-to-one translation for the client and then it'll work fine.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, in PIX 6.3 code (not released yet), there is supposed to be support for IPSec thru PAT (IPSec passthru), so watch out for it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jul 2002 02:19:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/configuring-pix-525-client-behind-pix-using-secureremote/m-p/67588#M620359</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2002-07-17T02:19:36Z</dc:date>
    </item>
  </channel>
</rss>

