Cyberduck Mountain Duck CLI

Opened on Mar 28, 2011 at 1:37:16 PM

Closed on Mar 29, 2011 at 5:55:36 AM

Last modified on Mar 17, 2015 at 7:12:05 AM

#5850 closed defect (worksforme)

illegal port command using FTPS transfer

Reported by: lee.norman@gmail.com Owned by: dkocher
Priority: normal Milestone: 4.1
Component: ftp-tls Version: 4.0.2
Severity: major Keywords:
Cc: Architecture: Intel
Platform: Mac OS X 10.6

Description

after upgrade to 4.0.2, every time I use FTP-SSL connection to transfer files from my transfer server, it errors out with illegal PORT command. I can use plain FTP to transfer file with no issue on this version.

I used 4.0.1 with no such error. There is no change in the ProFTPD version used on the server side, still 1.3.3a.

I set the Severity to high because I cannot transfer using FTP-SSL anymore.

Thanks in advance for looking into this problem. I have uploaded the log drawer transcript.

Attachments (1)

illegal port.txt​ (6.0 KB) - added by lee.norman@gmail.com on Mar 28, 2011 at 1:37:58 PM.
transcript from log draw that are port of the illegal port command. after upgrade to 4.0.2

Download all attachments as: .zip

Change History (6)

Changed on Mar 28, 2011 at 1:37:58 PM by lee.norman@gmail.com

transcript from log draw that are port of the illegal port command. after upgrade to 4.0.2

comment:1 Changed on Mar 29, 2011 at 5:55:36 AM by dkocher

  • Milestone set to 4.0.3
  • Resolution set to worksforme
  • Status changed from new to closed

Switch to ​passive (PASV) connect mode.

comment:2 follow-up: Changed on Mar 29, 2011 at 11:49:01 AM by lee.norman@gmail.com

Hi - I have not change the bookmark since I upgraded to V4.0.2... wondering why it worked before. I have tried to set it to PASV mode and it worked OK. For plain FTP, ACTIVE mode worked just fine. Sounded like an issue... but I got an resolution. Not a problem anymore.

comment:3 in reply to: ↑ 2 Changed on Mar 29, 2011 at 11:54:59 AM by dkocher

Replying to lee.norman@…:

Hi - I have not change the bookmark since I upgraded to V4.0.2... wondering why it worked before. I have tried to set it to PASV mode and it worked OK. For plain FTP, ACTIVE mode worked just fine. Sounded like an issue... but I got an resolution. Not a problem anymore.

This change was made in r8557. We have no more an automatic fallback for general FTP errors when opening data sockets.

comment:4 Changed on Jun 2, 2011 at 3:37:46 PM by dkocher

  • Milestone changed from 4.0.3 to 4.1

Milestone 4.0.3 deleted

comment:5 Changed on Mar 17, 2015 at 7:12:05 AM by ucodice

Full Complete solution for "ftp 500 Illegal PORT command". Click the following link:

​http://www.ucodice.com/articles/ftp-500-illegal-port-command/

Note: See TracTickets for help on using tickets.