I'm not sure if my problem is related or not. I doubt it, but I'm running out of ideas.

I am attempting to push a ~35MB file from a Windows machine to a remote Linux box, using rsync over SSH (using cwRsync on Windows 7).

The upload fails at almost the exact same point in the transfer, every single time (~10MB uploaded).

There is plenty of free disk space on the receiving end.

Throttling the connection speed with --bwlimit is not an acceptable countermeasure, as I have no idea what the client bandwidth capabilities might be in any given situation, but doing so does not help the situation, anyway.

If I reduce the bandwidth limit, even less of the file is copied. This leads one to conclude that the failure point is related more to time elapsed than to data transferred. This explains why the failure point is virtually identical every time, provided that the same transfer rate applies to each attempt. The "time-out" seems to be exactly 90 seconds.

I suspect that the problem is the crummy mediaTemple (gs) server to which I am uploading. Not being able to upload a 35MB file is pretty pathetic. I would like to force them to change their time-out policy. What setting do they appear to have modified to enforce this 90-second time-out? I wonder if any operation that takes more than 90 seconds on these crummy virtual machines is killed.

Thanks for any help!

Please don't resurrect ancient threads. This is a software issue, but could involve a problem with Windows 7. I moved your post to a new thread in General since it may be a Windows 7 problem.