<?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 FTP and AAA in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ftp-and-aaa/m-p/63750#M818</link>
    <description>&lt;P&gt;I am recently upgraded to 6.1(4) and I noticed that I have an issue with ftp.  When ever I connect to an FTP server on the internet I can not dowload anything. I am also using AAA with Cisco ACS 2.6(4).  I found a bug on the cisco site (CSCdx81167)&lt;/P&gt;&lt;P&gt;Sympton: FTP session would fail if PIX(v6.2.1) AAA is enabled and client connect to a FTP site with long banner &lt;/P&gt;&lt;P&gt;(approximate 600bytes or longer) before or after logon prompt. This is because the banner was truncated, and the&lt;/P&gt;&lt;P&gt; truncated portion includes the FTP response code such as '230' and the CR/LF. Solution: Remove the banner size limitation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only question is how to remove the banner size limitation.  I tried no fixup protocol 21 and it did not work. Am I missing something?&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 18:03:08 GMT</pubDate>
    <dc:creator>mtumarinson</dc:creator>
    <dc:date>2020-02-21T18:03:08Z</dc:date>
    <item>
      <title>FTP and AAA</title>
      <link>https://community.cisco.com/t5/network-access-control/ftp-and-aaa/m-p/63750#M818</link>
      <description>&lt;P&gt;I am recently upgraded to 6.1(4) and I noticed that I have an issue with ftp.  When ever I connect to an FTP server on the internet I can not dowload anything. I am also using AAA with Cisco ACS 2.6(4).  I found a bug on the cisco site (CSCdx81167)&lt;/P&gt;&lt;P&gt;Sympton: FTP session would fail if PIX(v6.2.1) AAA is enabled and client connect to a FTP site with long banner &lt;/P&gt;&lt;P&gt;(approximate 600bytes or longer) before or after logon prompt. This is because the banner was truncated, and the&lt;/P&gt;&lt;P&gt; truncated portion includes the FTP response code such as '230' and the CR/LF. Solution: Remove the banner size limitation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only question is how to remove the banner size limitation.  I tried no fixup protocol 21 and it did not work. Am I missing something?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:03:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ftp-and-aaa/m-p/63750#M818</guid>
      <dc:creator>mtumarinson</dc:creator>
      <dc:date>2020-02-21T18:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: FTP and AAA</title>
      <link>https://community.cisco.com/t5/network-access-control/ftp-and-aaa/m-p/63751#M819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the banner size limitation is within the pix code, not something that can be configured. the solution relates to the engineering fix within the code. you will need to obtain a fixed version when it becomes available to prevent this problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Sep 2002 04:17:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ftp-and-aaa/m-p/63751#M819</guid>
      <dc:creator>pgolding</dc:creator>
      <dc:date>2002-09-03T04:17:13Z</dc:date>
    </item>
  </channel>
</rss>

