IFTP and active FTP

#1
This problem remains, but has changed. With build 54 ...

With 'iftp "ftp://lucky/4plugins/test"', 'do i=8 to 20 ( copy ftp:%i.bin )' still fails for files big enough (426 Data connection unexpectedly closed), but now, for smaller files bigger than one packet, 1360 bytes are saved (as opposed to 1460 previously).
 
Last edited:
#4
Code:
[C:\test]ver /r & iftp "ftp://lucky.syr.edu/4plugins/test" & do i=8 to 20 ( copy /q ftp:%i.bin ) & dir & iftp /c

TCC  16.03.53 x64   Windows 7 [Version 6.1.7601]
TCC Build 53   Windows 7 Build 7601  Service Pack 1
Registered to Charles S. Galloway - 5 System License
TCC: FTP protocol error: 426 Data connection unexpectedly closed, file transfer /4plugins/test/18.bin aborted by client. "/4plugins/test/18.bin"
TCC: FTP protocol error: 426 Data connection unexpectedly closed, file transfer /4plugins/test/19.bin aborted by client. "/4plugins/test/19.bin"
TCC: FTP protocol error: 426 Data connection unexpectedly closed, file transfer /4plugins/test/20.bin aborted by client. "/4plugins/test/20.bin"

Volume in drive C is Win7_Galloway   Serial number is aea6:a855
Directory of  C:\test\*

6/23/2014  21:26         <DIR>    .
6/23/2014  21:26         <DIR>    ..
6/04/2014  21:52             256  8.bin
6/04/2014  21:52             512  9.bin
6/04/2014  21:52           1,024  10.bin
6/04/2014  21:52           1,460  11.bin
6/04/2014  21:52           1,460  12.bin
6/04/2014  21:52           1,460  13.bin
6/04/2014  21:52           1,460  14.bin
6/04/2014  21:52           1,460  15.bin
6/04/2014  21:52           1,460  16.bin
6/04/2014  21:52           1,460  17.bin
            12,012 bytes in 10 files and 2 dirs    40,960 bytes allocated
   351,830,556,672 bytes free

[C:\test]
Passive FTP is OFF. If PassiveFTP is ON - the results are as expected....
 
#5
Code:
[C:\test]ver /r & iftp "ftp://lucky.syr.edu/4plugins/test" & do i=8 to 20 ( copy /q ftp:%i.bin ) & dir & iftp /c

TCC  16.03.54 x64   Windows 7 [Version 6.1.7601]
TCC Build 54   Windows 7 Build 7601  Service Pack 1
Registered to Charles S. Galloway - 5 System License
TCC: FTP protocol error: 426 Data connection unexpectedly closed, file transfer /4plugins/test/18.bin aborted by client. "/4plugins/test/18.bin"
TCC: FTP protocol error: 426 Data connection unexpectedly closed, file transfer /4plugins/test/20.bin aborted by client. "/4plugins/test/20.bin"

Volume in drive C is Win7_Galloway   Serial number is aea6:a855
Directory of  C:\test\*

6/23/2014  21:36         <DIR>    .
6/23/2014  21:36         <DIR>    ..
6/04/2014  21:52             256  8.bin
6/04/2014  21:52             512  9.bin
6/04/2014  21:52           1,024  10.bin
6/04/2014  21:52           1,460  11.bin
6/04/2014  21:52           1,460  12.bin
6/04/2014  21:52           1,460  13.bin
6/04/2014  21:52           1,460  14.bin
6/04/2014  21:52           1,460  15.bin
6/04/2014  21:52           1,460  16.bin
6/04/2014  21:52           1,460  17.bin
6/04/2014  21:52           1,985  19.bin
            13,997 bytes in 11 files and 2 dirs    45,056 bytes allocated
   350,820,823,040 bytes free

[C:\test]
b54 doesn't work if PassiveFTP is OFF....
 
#10
Same here. Having used

mv "ftp://%admin%:%admin_pass%@%server%/%archive%" .

for a long time, it stopped working (don't remember the version, maybe 49). Then it was fixed, and has reappeared with 54 (or before).
Whichever version it was, right now I have to resort to a plethora of "real" FTP commands to get the job done...

Would be nice to see that fixed.
 

rconn

Administrator
Staff member
May 14, 2008
10,588
97
#11
Same here. Having used

mv "ftp://%admin%:%admin_pass%@%server%/%archive%" .

for a long time, it stopped working (don't remember the version, maybe 49). Then it was fixed, and has reappeared with 54 (or before).
Whichever version it was, right now I have to resort to a plethora of "real" FTP commands to get the job done...
Do you have passive FTP turned off? (And if so, why?)
 
#14
Rex, FWIW, in spite of your router's firewall, you should be able to test this by turning on the Windows FTP server and IIS management console features. With very little effort, and with no messing with the firewall, you should be able to connect on the localhost interface. I did so and again observed the problem with active FTP and IFTP. In fact, the firewall wasn't messed with automatically at all. So that I could test from the outside, I had to manually enable all the FTP-associated built-in rules. And even that wasn't enough. I noticed that the outbound rule specified only port 20. Only when I added my own rule for local port 21 outbound could I connect from work.
upload_2014-6-26_17-27-6.png