<?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 ASA 5505 FTP issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5505-ftp-issues/m-p/1776379#M496733</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The logs show that a device on the inside of the network is sending a reset on the control channel (TCP/21). Because your ASA is configured for FTP inspection, it also closes the child (data) connections along with it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest setting up packet captures to determine which device is actually sending the reset, and then find out why. Here is a guide that will help with ASA captures:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-1222"&gt;https://supportforums.cisco.com/docs/DOC-1222&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Oct 2011 13:26:25 GMT</pubDate>
    <dc:creator>mirober2</dc:creator>
    <dc:date>2011-10-07T13:26:25Z</dc:date>
    <item>
      <title>ASA 5505 FTP issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-ftp-issues/m-p/1776378#M496730</link>
      <description>&lt;P style="padding: 0pt; margin: 0pt;"&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding: 0pt; margin: 0pt;"&gt;I was wondering if anyone could make sense of the attached screen shot of the real time log?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding: 0pt; margin: 0pt;"&gt;We have a music system which moves updated tracks and changes using FTP, but we have never been able to get them working over VPN using ASA firewalls.&amp;nbsp; Using a PIX 501s they work fine and i have just upgraded the ASA to 8.2(5) but it still have the problem.&amp;nbsp; Traffice seems to start and then get dropped leaving the files with a 0byte size, although aleast 1 small file is always sucsessful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding: 0pt; margin: 0pt;"&gt;Any help would be appriciated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding: 0pt; margin: 0pt;"&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding: 0pt; margin: 0pt;"&gt;David&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:32:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-ftp-issues/m-p/1776378#M496730</guid>
      <dc:creator>David Shearing</dc:creator>
      <dc:date>2019-03-11T21:32:33Z</dc:date>
    </item>
    <item>
      <title>ASA 5505 FTP issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-ftp-issues/m-p/1776379#M496733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The logs show that a device on the inside of the network is sending a reset on the control channel (TCP/21). Because your ASA is configured for FTP inspection, it also closes the child (data) connections along with it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest setting up packet captures to determine which device is actually sending the reset, and then find out why. Here is a guide that will help with ASA captures:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-1222"&gt;https://supportforums.cisco.com/docs/DOC-1222&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Oct 2011 13:26:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-ftp-issues/m-p/1776379#M496733</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2011-10-07T13:26:25Z</dc:date>
    </item>
  </channel>
</rss>

