Opened 14 years ago

Closed 14 years ago

Last modified 10 years ago

#5131 closed Bug report (rejected)

ACTIVE mode no longer working

Reported by: mark Owned by:
Priority: normal Component: FileZilla Client
Keywords: ACTIVE MODE Cc:
Component version: Operating system type: Windows
Operating system version: Windows NT


Updated my installation to version 3.3.1 on Saturday.

FileZilla Client

Version: 3.3.1

Build information:

Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2010-01-03
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.10
GnuTLS: 2.8.3

I maintain three Windows Sites at AMHOSTING.COM. These all require ACTIVE transfer mode. Now, all three sites no longer work with FileZilla.

The earlier version worked fine.
Native FTP sessions with (from Windows NT; Windows Vista 32 and 64 bit)
FTP sessions using SMARTFTP (using ACTIVE transfer) work fine.

Your latest version doesn't work.
Here is a log Filezilla ... and SMARTFTP

Status: Resolving address of
Status: Connecting to
Status: Connection established, waiting for welcome message...
Response: 220 Microsoft FTP Service
Response: 331 Password required for XXXXXX.
Command: PASS
Response: 230 User XXXXXX logged in.
Status: Connected
Status: Retrieving directory listing...
Command: CWD /httpdocs
Response: 250 CWD command successful.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 24,211,50,212,5,57
Response: 500 Invalid PORT Command.
Command: PASV
Response: 227 Entering Passive Mode (204,10,137,244,10,195).
Command: LIST
Response: 425 Can't open data connection.
Error: Failed to retrieve directory listing

[03:49:21] SmartFTP v4.0.1072.0
[03:49:21] Resolving host name ""
[03:49:21] Connecting to Port: 21
[03:49:21] Connected to
[03:49:21] 220 Microsoft FTP Service
[03:49:21] USER XXXXXX
[03:49:21] 331 Password required for XXXXXX.
[03:49:21] PASS (hidden)
[03:49:21] 230 User XXXXXX logged in.
[03:49:21] SYST
[03:49:21] 215 Windows_NT
[03:49:21] Detected Server Type: Windows NT
[03:49:21] RTT: 124.972 ms
[03:49:21] FEAT
[03:49:22] 211-FEAT
[03:49:22] SIZE
[03:49:22] MDTM
[03:49:22] 211 END
[03:49:22] TYPE I
[03:49:22] 200 Type set to I.
[03:49:22] REST 0
[03:49:22] 350 Restarting at 0.
[03:49:22] PWD
[03:49:22] 257 "/" is current directory.
[03:49:22] CWD /httpdocs
[03:49:23] 250 CWD command successful.
[03:49:23] PWD
[03:49:23] 257 "/httpdocs" is current directory.
[03:49:23] TYPE A
[03:49:23] 200 Type set to A.
[03:49:23] PORT 192,168,1,104,5,62
[03:49:23] 200 PORT command successful.
[03:49:23] LIST -aL
[03:49:23] 150 Opening ASCII mode data connection for /bin/ls.
[03:49:23] 3296 bytes transferred. (24.7 KB/s) (130 ms)
[03:49:23] 226 Transfer complete.
[03:49:23] MDTM _vti_inf.html
[03:49:24] 213 20091110104827
[03:49:24] Time zone offset: -28800 seconds (-8.0 hours)


Change History (1)

comment:1 by Tim Kosse, 14 years ago

Resolution: rejected
Status: newclosed

There's nothing wrong with the PORT command sent by FileZilla.

Two possibilities:
1) Some malicious router and/or firewall is actively sabotaging the PORT command so that something else gets received by the server that hasn't been sent by FileZilla
2) Broken server

In the former case, read, in the latter case contact the server administrator for assistance.

Note: See TracTickets for help on using tickets.