<?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: CSS and non standard ftp port in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335146#M5507</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You'll need to move the FTP server to a standard port for now. See CSCeb22950.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Sep 2004 05:01:40 GMT</pubDate>
    <dc:creator>kevin.graham</dc:creator>
    <dc:date>2004-09-09T05:01:40Z</dc:date>
    <item>
      <title>CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335145#M5506</link>
      <description>&lt;P&gt;We have an ftp server running on port 10021.  Is there a way to have the CSS translate the IP in the payload when not using port 21?  On an IOS router one can use the ip nat service command.  I have not seen anything like this on the CSS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We currently have a VIP and a sourcegroup with matching IP's configured for the ftp server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2004 20:21:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335145#M5506</guid>
      <dc:creator>clayton-price</dc:creator>
      <dc:date>2004-09-08T20:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335146#M5507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You'll need to move the FTP server to a standard port for now. See CSCeb22950.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 05:01:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335146#M5507</guid>
      <dc:creator>kevin.graham</dc:creator>
      <dc:date>2004-09-09T05:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335147#M5508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kevin, this bug applies to CSM - not CSS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 11:14:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335147#M5508</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-09-09T11:14:37Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335148#M5509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Clayton,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;try to use the command 'application ftp' in the content rule definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 11:15:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335148#M5509</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-09-09T11:15:09Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335149#M5510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That seemed to resolve the fact that the address in the ftp payload was not being translated.  However....Our ftp server is configured to tell clients to connect on ports 8550-8650.  It seems that the content switch is passing a port outside this range back to the client.  The CSS then maps the port it sent to the client to a port in the range of 8550-8650.  Is there a way to have the CSS pass the port specified by the server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Clayton&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 14:05:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335149#M5510</guid>
      <dc:creator>clayton-price</dc:creator>
      <dc:date>2004-09-09T14:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335150#M5511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Configure your VIP for port 21 traffic and the service for port 10021.&lt;/P&gt;&lt;P&gt;service HP17_5001 &lt;/P&gt;&lt;P&gt;  ip address 10.254.236.7 &lt;/P&gt;&lt;P&gt;  protocol tcp &lt;/P&gt;&lt;P&gt;  port 10051 &lt;/P&gt;&lt;P&gt;  active &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;content DDN1 &lt;/P&gt;&lt;P&gt;    vip address 192.67.251.15 &lt;/P&gt;&lt;P&gt;    port 21 &lt;/P&gt;&lt;P&gt;    protocol tcp &lt;/P&gt;&lt;P&gt;    add service HP17_5001 &lt;/P&gt;&lt;P&gt;    application ftp-control &lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope ths helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 14:51:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335150#M5511</guid>
      <dc:creator>jnorman</dc:creator>
      <dc:date>2004-09-09T14:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335151#M5512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I appreciate all the responses!  In this case the CSS is also translating the high order port the server informs clients to connect to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm likely going to configure a port 21 VIP in addition to the port 10021 VIP in order to get around some other firewall issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2004 18:02:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335151#M5512</guid>
      <dc:creator>clayton-price</dc:creator>
      <dc:date>2004-09-09T18:02:44Z</dc:date>
    </item>
    <item>
      <title>Re: CSS and non standard ftp port</title>
      <link>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335152#M5513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Clayton,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is normal behavior.&lt;/P&gt;&lt;P&gt;CSS changes TCP ports.&lt;/P&gt;&lt;P&gt;There is no way to prevent this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Sep 2004 06:38:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-and-non-standard-ftp-port/m-p/335152#M5513</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-09-10T06:38:53Z</dc:date>
    </item>
  </channel>
</rss>

