252b2 - FTP won't connect with changed ports

[vld]

If I change the default port from 21 to 10156, the FTP client just hangs and will not display the window contents.

[Jan Rysavy]

The 2.52b1 works fine?

[vld]

I quit using 2.52b1 and went back to 2.51. V2.51 has the same problem.

[Jan Rysavy]

So it looks like some old problem. Does it work in another FTP client, for example FileZilla?

[vld]

FileZilla works perfect

[Petr Solin]

I have just tried to change listen port of my local FTP server to 10156 and all works well (FTP client connects from my machine and from another local network machine too), so I'm not able to reproduce this problem. Please try to send me more details on how to reproduce this problem.

Does anyone else have this problem?

[vld]

I just tested it again. All I did is set up a normal FTP connection and changed the port to 10156. I connect but when I try and get the directory listing, I get this:



I tried playing around with different settings in the advanced tab and no changes.

[Ether]

Could you post the log of that connection attempt from Salamander (Plugins > FTP Client > Show Logs) and FileZilla? IMO it's a problem on the server side. It seems that FileZilla uses some kind of error recovery mechanism to circumvent this, but Salamander's FTP Client does not. I've seen something similar before with an improperly configured NAS FTP server (thread about FTP PASV IP autodetection, it's in Czech, but at least the logs are self-explanatory).

[vld]

Here's the Altap log:

Code: Select all

Connecting to "[....ftp site.....]" ([....IP ADDRESS.....]) on port 10156.
Log UID is 0, time is 9/21/2009 - 9:34:29 AM.

220-Welcome
220 Service ready for new user
USER [....UserName.....]
331 Password required
PASS (hidden)
230 User logged in
(9:34:34): Logged in successfully, getting system information...
SYST
215 MACOS Peter's Server
PWD
257 "/" is current directory.
(9:34:34): Changing path to "/"...
(9:34:34): Listing path "/"...
PORT [....IpAdd.....],4,76
200 PORT command successful
TYPE A
200 Type set to A (ASCII)
LIST
150 Opening connection
(9:35:04): Sending or aborting of list command has timed out. Note: if data transfer was not started, try to
change transfer mode (see Connect to FTP Server dialog > Advanced > Use passive transfer mode)

-----

Reconnecting to "[....ftp site.....]" (....IP ADDRESS.....) on port 10156 (attempt no. 2).
Time is 9/21/2009 - 9:35:24 AM.

220-Welcome
220 Service ready for new user
USER [....UserName.....]
331 Password required
PASS (hidden)
230 User logged in
(9:35:25): Logged in successfully, getting system information...
SYST
215 MACOS Peter's Server
CWD /
250 CWD command successful
PWD
257 "/" is current directory.
PORT [....IpAdd.....],4,112
200 PORT command successful
TYPE A
200 Type set to A (ASCII)
LIST
150 Opening connection
(9:35:41): Operation canceled by user.
(9:35:41): Text listing was parsed by "IBM z/VM (CMS) 1" server type...

I don't have Filezilla installed anymore.

[Jan Patera]

Here's the Altap log:
I don't have Filezilla installed anymore.

Could you also try the passive mode as the message box suggests and post the log as well?

[Ether]

I don't have Filezilla installed anymore.

Well, I'm kinda lost without the opportunity of comparing logs from a working and a not working client. I'd appreciate very much, if you could download the FileZilla Client (FileZilla Download page, look for _3.x.x.x_win32.zip - that's a non-installer version) and post the log.

And of course, as Jan says, try the passive mode if you haven't already.

[vld]

Passive mode

Code: Select all

220-Welcome
220 Service ready for new user
USER [....UserName.....]
331 Password required
PASS (hidden)
230 User logged in
(11:56:06): Logged in successfully, getting system information...
SYST
215 MACOS Peter's Server
PWD
257 "/" is current directory.
(11:56:06): Changing path to "/"...
(11:56:06): Listing path "/"...
PASV
227 Entering Passive Mode (........)
TYPE A
200 Type set to A (ASCII)
LIST
150 Opening connection
(11:56:16): Operation canceled by user.
(11:56:16): Text listing was parsed by "Microsoft IIS" server type...

FileZilla v3.2.7.1

Code: Select all

Status:	Connecting to .......................
Status:	Connection established, waiting for welcome message...
Response:	220-Welcome
Response:	220 Service ready for new user
Command:	USER .......
Response:	331 Password required
Command:	PASS *****
Response:	230 User logged in
Command:	SYST
Response:	215 MACOS Peter's Server
Command:	FEAT
Response:	211-Extensions supported:
Response:	 SIZE
Response:	 REST STREAM
Response:	 APPE
Response:	 MDTM
Response:	 MACB
Response:	 PBSZ
Response:	 PROT
Response:	 EPSV
Response:	211 End
Status:	Connected
Status:	Retrieving directory listing...
Command:	PWD
Response:	257 "/" is current directory.
Command:	TYPE I
Response:	200 Type set to I (Image)
Command:	PASV
Response:	227 Entering Passive Mode (..............)
Status:	Server sent passive reply with unroutable address. Using server address instead.
Command:	LIST
Response:	150 Opening connection
Response:	226 Transfer complete
Status:	Directory listing successful

[Ether]

Code: Select all

Command:	PASV
Response:	227 Entering Passive Mode (..............)
Status:	Server sent passive reply with unroutable address. Using server address instead.

As I suspected, this is a problem on the server side. The server expects the client to connect to an "invalid" address. I suggest you try to fix the server or contact its administrator about that.

However, judging from the increasing popularity of this problem, I recommend that FTP plugin have an option similar to FileZilla Client to try connecting to the server's external IP address in case the server provides a bad one.

[Jan Rysavy]

How is this problem connected to PORT number?
It works on 21 but doesn't on 10156.

[vld]

Is it possible by changing the port number, some other setting in the plugin gets screwed up causing it not to work????