[comp.protocols.tcp-ip] ARPANET<->MILNET problems

PAP4@AI.AI.MIT.EDU ("Philip A. Prindeville") (11/09/87)

    Date: 5 Nov 87 07:37:27 GMT
    From: jbs@eddie.mit.edu  (Jeff Siegal)

    I've been trying to ftp some files from ECLA.USC.EDU (on MILNET) to
    MIT (on ARPANET) and have had no success for the past week.  The Unix
    ping program reports round-trip-times of 20-40 seconds and packet
    loss rates varying between 70 and 100 percent.

    Is there some current problem that is likely to be corrected, or
    should we give up and resort to Federal Express and magtape?

    Jeff Siegal

I have been having similar problems to Jeff's.  I have been trying to
reach a couple of hosts at CMU, with little success.  FTPs and TELNETs
timeout before the connection is established.  None of my pings have
gotten through.  On the few occasions (2 or 3 times in many hours) that
my FTPs did connect, logging in took about 2 minutes, and getting a 14k
file took more than 40 minutes, sometimes not even finishing...

Reaching the NIC has not been a problem, though.  Is this a side
effect of 7.1 or isolated problems?  I haven't been able to reach
the NOC, but will call them Monday...

-Philip

nemnich@NRL-CMF.ARPA (11/13/87)

I have had the misfortune of having to cross the MILNET/ARPANET boundary for
the past two months.  I don't think the problems are related to the new PSN
software, since I am not seeing that much of a difference since it was
installed.  Also, things are moving right along when I stay on the MILNET or
the ARPANET.  The gateways must be incredibly overloaded; I see lots of packet
loss when pinging across the boundary.

A question for those with the data: How evenly spread is the load among the
ARPA/MILNET gateways?

--Bruce Nemnich, Thinking Machines Corporation, Cambridge, MA
  Temporarily at NRL, Washington, DC: +1 202 767 9044
  bruce@think.com, ihnp4!think!bruce, bjn@mitvma.bitnet