<?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: FWSM Blocking FTP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-blocking-ftp/m-p/1243678#M840863</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Update: Received help from TAC and turns out to be an issue with 3.1(4) code. Upgraded to 4.0.4 code as TAC recommended which resolved the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rommel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Aug 2009 16:38:00 GMT</pubDate>
    <dc:creator>uchideshi</dc:creator>
    <dc:date>2009-08-12T16:38:00Z</dc:date>
    <item>
      <title>FWSM Blocking FTP</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-blocking-ftp/m-p/1243676#M840861</link>
      <description>&lt;P&gt;I have a FWSM running 3.1.4 that has an outside and inside interface. There is a server 146.22.x.x on the outside that needs to ftp to 146.27.y.y The FW buffer log shows access-list outside is denying the traffic. I look at access-list outside and the very first line allows 146.22.x.x to 146.27.y.y I add an ACE on top to allow any tcp from 146.22.x.x to 146.27.y.y but still gets the denies in the log. I pipe the hex number on the deny info and it shows that the ACL denying the traffic is my explicit deny ip any any on line 91 of access-list outside. I am using the default class-map and policy-map. FTP is being inspected under the default map. Nat control is turned off on this FWSM. Any suggestions on how to troubleshoot this issue? Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rommel&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:35:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-blocking-ftp/m-p/1243676#M840861</guid>
      <dc:creator>uchideshi</dc:creator>
      <dc:date>2019-03-11T15:35:17Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Blocking FTP</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-blocking-ftp/m-p/1243677#M840862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Without seeing the logs, I can only hazard a guess.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are the ports of the denied traffic?  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 24 May 2009 23:38:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-blocking-ftp/m-p/1243677#M840862</guid>
      <dc:creator>mmacdonald70</dc:creator>
      <dc:date>2009-05-24T23:38:47Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Blocking FTP</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-blocking-ftp/m-p/1243678#M840863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Update: Received help from TAC and turns out to be an issue with 3.1(4) code. Upgraded to 4.0.4 code as TAC recommended which resolved the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rommel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Aug 2009 16:38:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-blocking-ftp/m-p/1243678#M840863</guid>
      <dc:creator>uchideshi</dc:creator>
      <dc:date>2009-08-12T16:38:00Z</dc:date>
    </item>
  </channel>
</rss>

