>>Does the file have to be 2.2GB? Maybe you could look into products that transmit file deltas rather than the entire file, if you are going to do this regularly and most of the file doesn't change.
>>
>>http://en.wikipedia.org/wiki/Rsync
>
>There is something in there that need to fixed. Once I find it, this should work as is as well.

Yes, there may be a setting or timeout somewhere that's making your download fail after 2 hours, and it's probably a good idea to track it down.

But, even if you do find it, it's worth thinking about what you're doing.

Even if your download is successful, it's going to take about 4 hours. That's a long time for a single computer operation, unexpected things can happen. You might want to look into fault-tolerant downloading such as implemented by so-called "download managers", that let you resume a failed download rather than having to start all over again.

If you really expect to regularly spend 4 hours on a single download you may have to check a lot of things to find the problem:

- other scheduled tasks running on the remote FTP server, or the remote site (backups, maintenance, ...)
- scheduled tasks running at your end - backups, antivirus scans, ...
- whether your ISP is monitoring or shaping traffic and has a limit of 2 hours for any single FTP download

Also, if you're transferring 55% of a 2.2GB file in 2 hours, that works out to about 1.3Mbps. While this is not likely saturating your download speed, it may well be saturating the upload speed of the FTP server if it has a typical asymmetric broadband link (DSL or cable). That could adversely affect other operations at the remote site - for a rather long period.

It would be a big win if you could reduce that file size. If you can use a file delta technique like rsync you might be able to reduce it by a factor of 10 or more. You could have the client send the first file via a USB stick, so you never have to worry about downloading the entire file.