Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!jwz@teak.berkeley.edu
From: jwz@teak.berkeley.edu (Jamie Zawinski)
Newsgroups: comp.sys.ti.explorer
Subject: flaky net connections
Message-ID: <31034@ucbvax.BERKELEY.EDU>
Date: 31 Aug 89 17:59:05 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 16


Often when I try to connect to another machine (via copy file, or telnet, 
or whatever) the connection times out.  Much of the time, hitting resume 
or reinvoking the command does no good; I get the "not responding" error
again right away, without another attempt to connect being made at all.

I've found that (sometimes) calling (NAME:REFRESH-CACHE NIL) will disrupt
whatever caching is going on enough that it will actually try to connect
again, but that doesn't always work, and is especially unreliable if the
connection is to an IP host.  Calling (IP:RESET T) usually fixes things,
but that takes a long time, and has the nasty side effect of closing any
other open connections...

So does anyone know a better way of dealing with this situation?

		-- Jamie