the fxp transfer with lftp does not work on certain servers. i put the
debug option to 9 and tried to sort out the problem. here my opinon:
*** after the two connection between the servers were etablished
following commands were exchanged:
(all IPs were replaced with xx.xx.xx.xx for server 1 and yy.yy.yy.yy
for server 2, login names and server names were replaced with
dummy contents)
-------- snipp: protocol begin lftp -----------
---> PASV
<--- 227 Entering Passive Mode (xx,xx,xx,xx,14,222)
---> RETR some_file_name.rar
---> PORT xx,xx,xx,xx,14,222
<--- 200 PORT Command successful.
---> STOR some_file_name.rar
<--- 150 Opening BINARY mode data connection for some_file_name.rar.
<--- 425 Can't open data connection.
---> QUIT
<--- 221- Goodbye
<--- 221
---- Schlie�e den Kontroll - Socket
---> ABOR
<--- 500 '�ABOR': command not understood.
**** server bug: 426 reply missed
<--- 425 Cannot open data connection.
---> SIZE some_file_name.rar
<--- 213 0
---- Schlie�e den Kontroll - Socket
---- Verbinde mit cowftp.dyndns.dk (yy.yy.yy.yy) Port 21
<--- 220-Serv-U FTP Server v3.0 for WinSock ready...
<--- 220-Welcome to cow's ftp
<--- 220-
<--- 220-This is a private ftp
<--- 220-
<--- 220 Have fun ;)
---> AUTH TLS
<--- 530 Not logged in.
---> USER road
<--- 331 User name okay, need password.
---> PASS XXXX
<--- 230 User logged in, proceed.
---> CWD /Incoming
<--- 250 Directory changed to /Incoming
---> TYPE I
<--- 200 Type set to I.
---> SIZE some_file_name.rar
<--- 213 0
---- Verbinde mit xx.xx.xx.xx (xx.xx.xx.xx) Port 27910
<--- 220 Baby of Bastard operator (glftpd 1.25_Linux) ready.
---> AUTH TLS
<--- 500 'AUTH TLS': Command not understood.
---> USER roadrunner
<--- 331 Password required for roadrunner.
---> PASS XXXX
<--- 230- `-----( Type 'site onel MESSAGE' to enter your message )-----'
<--- 230 User roadrunner logged in.
---> CWD /complete/the_directory_where_the_files_are
<--- 250- --NEWS--
<--- 250-
<--- 250- New Feature: Login with (!)Username to kill ghost connections.
<--- 250- New Feature: aSFV sfv-checker added. report any probs to deadlock.
<--- 250- New Feature: dirmover script added. complete dirs automoved to /complete.
<--- 250- download from /incoming at your own risk!
<--- 250-
<--- 250- --=- Type SITE HELP for a nice list of SITE commands -=--
<--- 250-
<--- 250 CWD command successful.
---> TYPE I
<--- 200 Type set to I.
---> PASV
<--- 227 Entering Passive Mode (xx,xx,xx,xx,14,224)
---> RETR some_file_name.rar
---> PORT xx,xx,xx,xx,14,224
<--- 200 PORT Command successful.
---> STOR some_file_name.rar
<--- 150 Opening BINARY mode data connection for some_file_name.rar.
<--- 425 Can't open data connection.
---> QUIT
<--- 221- Goodbye
<--- 221
---- Schlie�e den Kontroll - Socket
---> ABOR
<--- 500 '�ABOR': command not understood.
**** server bug: 426 reply missed
<--- 425 Cannot open data connection.
---> SIZE some_file_name.rar
<--- 213 0
---- Schlie�e den Kontroll - Socket
---- Verbinde mit cowftp.dyndns.dk (yy.yy.yy.yy) Port 21
------------ end of lftp protcol --------------------------------------
using another fxp client (profxp) i was able to transfer the file and
i got this protocol.
------------ snipp: protocol begin profxp ------------------------------
>> PASV
<< 227 Entering Passive Mode (xx,xx,xx,xx,15,1)
>> PORT xx,xx,xx,xx,15,1
<< 200 PORT Command successful.
>> STOR some_file_name.rar
<< 150 Opening BINARY mode data connection for some_file_name.rar.
>> RETR some_file_name.rar
!! STOR/RETR failed (timeout/firewall/permission problem ?)
:: >>> Waiting for ABORT to finish <<<
<< 500 '�ABOR': command not understood.
:: attempting to resync server
:: attempting to resync server
?? now trying other FXP mode
>> PASV
<< 227 Entering Passive Mode (yy,yy,yy,yy,12,250)
>> PORT yy,yy,yy,yy,12,250
<< 200 PORT command successful.
>> RETR some_file_name.rar
<< 150 Opening BINARY mode data connection for some_file_name.rar (1542 bytes).
>> STOR some_file_name.rar
<< 150 Opening BINARY mode data connection for some_file_name.rar.
:: >>> XFER running, hit 'a' to abort, 's' to stop after current file <<<
<< 226 Transfer complete.
------------ end of profxp protcol --------------------------------------
as we see both programms try to set 1st the passive mode for the
source. and it does not work. but switching to the 2nd method (passive
destination) profxp is able to transfer the file. lftp is not.
there are some observations:
1) profxp does not send a QUIT command to any of the servers (so there
is no need for a reconnect) --- not sure why lftp is sending the
QUIT/ABOR. but i suppose it has nothing to do with the fxp
transfer. the only difference is that lft has to reconnect to both
servers again (which it does).
2) lftp is using following command sequence
a) PASV
b) STOR (RETR)
c) PORT
d) RETR (STOR)
whereas profxp is using this sequence:
a) PASV
b) PORT
c) STOR (RETR)
d) RETR (STOR)
not sure if there is a "proper" command sequence but the one of profxp
is working.
i had this problem with a couple server now. could anyone take a look
into it. thx.
mfg Max Hofer
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Ihre E-Mail noch individueller? - http://domains.yahoo.de
