FTP Server Timeout

ShiverinEskimo

Downloading Linux ISO's from heanet.ie ftp using SmartFTP v1.0
After about 20 minutes it gives me a server timeout error and stops downloading.
I was hoping to leave it downloading for the 3 hours it wants and come back to a successful download but the server keeps timing out. (twice so far).

Is this normal? I mean why host such a large file (640mb) when it is nigh on impossible to download it in 20 minutes. I have an average connection of 56kb/s and it has never dropped below 40 and has even peaked to 70 according to DU Meter Stopwatch.

Is it some setting on SmartFTP that is causing this or do heanet not like people downloading for more than 20 mins at a time?

Any ideas welcome...

Cheers,
Shiv.

ShiverinEskimo

Now its rufusing my resume request
Aaarrrgh, why host a file that size if you don't like people downloading.

(still open to advice telling me its my fault)

Chalk

they may be timing you out as your connection may appear to be inactive.
the transfer only registers as an action at the start (i think )

ftp client should have a "keep alive" or similar section in the options
it just send some request to the server every 20 mins to refresh the folder your viewing

if it doesnt try filezilla
http://filezilla.sourceforge.net/
never had problems with that

Mutant_Fruit

Firstly ditch smart FTP. What you really need in this situation is something like Getrightr. Any download resumer will do, but thats the one of my choice.

Start downloading the file through Getright, and set it to download 8 chunks, and make sure you get some alternate download locations (just click onthe search for mirrors button). THen you should have no problem maxing out your connection. And if one server gives ya problems, getright will switch to other ones.

ShiverinEskimo

In the process of looking into getright

I found the keep alive settings in smartFTP. It is set to keep alive and send the command "NOOP" to the server. However the server seems not to recognise such a command and gives an error. Should this still keep me alive or would it kill me on the basis that unrecognised commands will not cause the server to reset its connection clock for me?

Chalk

not sure
id reckon an unrecognised command could be interpreted as interaction by the server
try setting it to say TYPE A or REST 0 or PWD
see if that makes a diff

ShiverinEskimo

Seems to be running nicely now. I disconnected completely and reconnected and changed the keep alive command to TYPE A.
22 minutes later i'm not kicked off.

*Touching wood*

Chalk

take it that it worked?

ShiverinEskimo

ish, i'm getting 50 minutes to an hour out of it now. still have to disconnect and reconnect from time to time. seems only to happen when i leave the pc for a while (typically).

Still not perfect...