Problem recognizing response 227?

Report client bugs
Post Reply
lubine
Posts: 4
Joined: Thu Jan 19, 2006 2:28 pm

Problem recognizing response 227?

Post by lubine »

I am connected to an FTP server over a (slow) GPRS link, the response to the PASV command seems to be misinterpreted by coreftp. It seems not to recognize the IP address. The port number however is correct.
The log:

PWD
257 "/Absfiles"
ASV
227 Entering Passive Mode (81,169,99,140,193,189)
LIST
Connect socket #580 to , port 49597...
timeout
Error loading directory...

When I connect to the same server using an ethernet connection, all works well. I have verified the 227 message with ethereal on the PC. It looks okay here:
0030 22 17 e3 9d 00 00 32 32 37 20 45 6e 74 65 72 69 ".....227 Enteri
0040 6e 67 20 50 61 73 73 69 76 65 20 4d 6f 64 65 20 ng Passive Mode
0050 28 38 31 2c 31 36 39 2c 39 39 2c 31 34 30 2c 31 (81,169,99,140,1
0060 39 33 2c 31 38 39 29 0d 0a 93,189)..

I am using coreftp version 1.3c, build 1446.
jeffd
Posts: 113
Joined: Thu May 06, 2004 6:12 am

Post by jeffd »

The message you are looking at is on the command channel which works ok if you got up to this point. The problem is in the data channel and it can't connect.

If you are on a slow connection you can change the timeout inthe global settings. Go to View -> Options -> Connections and increase the connection timeout to 60.

If it doesn't work then its a firewall problem somewhere along the line.
lubine
Posts: 4
Joined: Thu Jan 19, 2006 2:28 pm

Problem recognizing response 227?

Post by lubine »

Look at the message where coreftp tells us that it will connect to the data port:
Connect socket #580 to , port 49597...
The IP address is missing! It should something like:
Connect socket #580 to 81.169.99.140, port 49597...
jeffd
Posts: 113
Joined: Thu May 06, 2004 6:12 am

Post by jeffd »

Is there anything in the advanced -> connection -> Use NAT IP/Address field? (could be spaces even).
lubine
Posts: 4
Joined: Thu Jan 19, 2006 2:28 pm

Post by lubine »

The "Use NAT IP/Address field" is empty. Even no spaces.
It is a log from the GUI.
I forgot to mention that is does work with another FTP client...
lubine
Posts: 4
Joined: Thu Jan 19, 2006 2:28 pm

Post by lubine »

Solved!
The problem was that the "Use NAT IP/Address" checkbox was checked. Although the field was empty.
I found this after I created a new connection with the connection manager, to the same server, and that worked....
Thanks guys.
Post Reply