Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!BBNCCV.ARPA!brescia
From: brescia@BBNCCV.ARPA (Mike Brescia)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Am I imagining things?
Message-ID: <8607011443.AA28612@ucbvax.Berkeley.EDU>
Date: Tue, 1-Jul-86 09:00:29 EDT
Article-I.D.: ucbvax.8607011443.AA28612
Posted: Tue Jul  1 09:00:29 1986
Date-Received: Wed, 2-Jul-86 00:02:44 EDT
References: <12219087923.5.MRC@SIMTEL20.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18
Approved: tcp-ip@sri-nic.arpa


          You aren't the first person to have complained about this.  I
     investigated it as a TOPS-20 problem but then I got reports that it
     happened in FTP transfers that didn't involve any TOPS-20 systems.  


Can you name a site to which an FTP hangs from your host, and another to which
it does not fail?  You could also list the gateway(s) through which your
connection passes.

Can you examine the TCP layer and IP layer statistics for signs of
retransmissions or missing acks (TCP) or discarded unreassembled fragments
(IP) or any other counters that are out of the mainstream?

I would like to see some indication from the host ends that the problem either
could or could not be caused by a gateway.

	Mike Brescia