<?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 Issues With Active Mode FTP through FTD in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/issues-with-active-mode-ftp-through-ftd/m-p/3951774#M935644</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are migrating from ASA 5525 to FTD 2110 running FTD/FMC 6.4.0.6 and cannot seem to get active-mode FTP to work through the FTD for a client on the inside connecting to an external Internet server on the outside.&amp;nbsp; The initial control channel works, but the data channel fails to connect (passive-mode FTP works ok).&amp;nbsp; With our ASA, as long as "inspect ftp" is enabled, the data channel gets pin holed through and NAT rewrite also occurs and active-mode FTP works.&amp;nbsp; I cannot seem to get the same functionality with the FTD.&amp;nbsp; I have confirmed that "inspect-ftp" is in the&amp;nbsp; global_policy, and have used either a port 21 match and/or an FTP application match in my ACP, and it still does not work with active-mode.&amp;nbsp; I also, read that another option is to use a prefilter/fastpath to bypass Snort, but this isn't working either.&amp;nbsp; I am suspecting a NAT issue, as I see the following in a Capture w/Trace:&lt;/P&gt;&lt;P&gt;Action: drop&lt;BR /&gt;Drop-reason: (nat-no-xlate-to-pat-pool) Connection to PAT address without pre-existing xlate&lt;/P&gt;&lt;P&gt;The NAT is an auto NAT with PAT configured the same as we have on our ASA.&amp;nbsp; Has anyone else successfully configured active-mode FTP through an FTD, and can offer some insight into what may be going on here?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 17:39:14 GMT</pubDate>
    <dc:creator>pncisco216</dc:creator>
    <dc:date>2020-02-21T17:39:14Z</dc:date>
    <item>
      <title>Issues With Active Mode FTP through FTD</title>
      <link>https://community.cisco.com/t5/network-security/issues-with-active-mode-ftp-through-ftd/m-p/3951774#M935644</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are migrating from ASA 5525 to FTD 2110 running FTD/FMC 6.4.0.6 and cannot seem to get active-mode FTP to work through the FTD for a client on the inside connecting to an external Internet server on the outside.&amp;nbsp; The initial control channel works, but the data channel fails to connect (passive-mode FTP works ok).&amp;nbsp; With our ASA, as long as "inspect ftp" is enabled, the data channel gets pin holed through and NAT rewrite also occurs and active-mode FTP works.&amp;nbsp; I cannot seem to get the same functionality with the FTD.&amp;nbsp; I have confirmed that "inspect-ftp" is in the&amp;nbsp; global_policy, and have used either a port 21 match and/or an FTP application match in my ACP, and it still does not work with active-mode.&amp;nbsp; I also, read that another option is to use a prefilter/fastpath to bypass Snort, but this isn't working either.&amp;nbsp; I am suspecting a NAT issue, as I see the following in a Capture w/Trace:&lt;/P&gt;&lt;P&gt;Action: drop&lt;BR /&gt;Drop-reason: (nat-no-xlate-to-pat-pool) Connection to PAT address without pre-existing xlate&lt;/P&gt;&lt;P&gt;The NAT is an auto NAT with PAT configured the same as we have on our ASA.&amp;nbsp; Has anyone else successfully configured active-mode FTP through an FTD, and can offer some insight into what may be going on here?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:39:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issues-with-active-mode-ftp-through-ftd/m-p/3951774#M935644</guid>
      <dc:creator>pncisco216</dc:creator>
      <dc:date>2020-02-21T17:39:14Z</dc:date>
    </item>
  </channel>
</rss>

