[Info-vax] preventing FTP from timing out

[Phillip Helbig---undress to reply]

In article <k4eo4f$d32$1 at dont-email.me>, Stephen Hoffman
<seaohveh at hoffmanlabs.invalid> writes: 

> On 2012-10-02 12:14:27 +0000, Phillip Helbig---undress to reply said:
> 
> >   HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 7
> > 
> > ########################################################
> > 
> > 421 Service not available, remote server timed out. Connection closed.
> > 122054124 bytes sent in 07:56 (250.35 KiB/s)
> > 
> > What causes this timeout?  (I thought one reason for hash was to keep
> > things from timing out.)  The connection is otherwise OK, as far as I
> > can tell.
> > 
> > Is there somehow I can increase the timeout?  At least if something is
> > actually being transferred, I don't want it to time out.
> 
> This is likely a bug, and not a feature.  And in general, timeouts are 
> not something to be adjusted; they're often precariously balanced and 
> changes to the defaults can have unexpected repurcussions.

OK.

> Your network is either screwed up, or (if the timeout is consistent) 
> you're dealing with an FTP client or server with a size limit or with a 
> bug.

Maybe just the message is wrong.  There were two attempts and, thanks to
VMS versions, I thus have both.  They are the same size.  Also, it
appears that the entire file was transferred.  So, maybe just the
message is wrong. 

> available space on the target disk, and fragmentation, etc.

No problems there.

> And given I routinely get vastly better speeds over WiFi connections, 
> this is definitely operating on lower-grade networking hardware.

This was across the Atlantic.  Not sure where the narrowest bottleneck
is.  At home (i.e. the receiving end) I have a 16 Mb/s DSL connection. 
The ALPHA has a 100 Mb/s ethernet card.  However, my wife was watching
television on an iPad on the same LAN, so that probably got some of the
bandwidth.  :-(