Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!BBN.COM!malis
From: malis@BBN.COM (Andy Malis)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: PSN weirdness
Message-ID: <8901232219.AA07995@ucbvax.Berkeley.EDU>
Date: 23 Jan 89 21:01:00 GMT
References: <8901111723.aa16077@SPARK.BRL.MIL>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 31

Terry,

I haven't seen a follow-up on the TCP-IP list since your original
message (I just got back from vacation) and I'm curious if you
are still experiencing the problem with ARDEC.ARPA.  I have a
ping running right now and the average time is running around 380
ms.  I'm getting about the same average for 26.0.0.45 as well
(this is through two gateways between the BBN internal net and
the MILNET).

Experiencing a longer round trip time for the first ping or two
is to be expected; the PSNs are in the process of setting up a
subnet end-to-end virtual circuit.  Once the connection has been
established, data flows.

The behavior you described (two hosts at the same PSN having
widely differing operating characteristics) usually points to
problems with an individual host: either a problem in the host
itself, or a hardware problem with its access line or port (on
either end of the line).

The folks at the CONUS NOC are usually very good at solving this
sort of problem, and are assisted by development folks up here in
Cambridge when necessary.  I suggest giving them another try if
this is still an ongoing problem.  If that fails, mail to tcp-ip
certainly gets attention, since it is read by both folks at the
DDN PMO and in BBNCC.

Regards,
Andy Malis
Manager, BBNCC PSN Development Support