C. Philip Wood (cpw%sneezy@LANL.GOV)
Wed, 14 Dec 88 14:47:56 MST
(UCLA/Mail V1.410 M-ACP-8280-37); Wed, 14 Dec 88 23:28:25 PST
Received: from VM.USC.EDU by MVSA.USC.EDU
with TCP; Wed, 14 Dec 88 23:28:24 PST
Received: from USCVM.BITNET by VM.USC.EDU (IBM VM SMTP R1.2) with BSMTP id 7324;
Wed, 14 Dec 88 23:29:55 PST
Received: by USCVM (Mailer X1.25) id 7321; Wed, 14 Dec 88 23:29:54 PST
Date: Wed, 14 Dec 88 14:47:56 MST
Reply-To: <TCP-IP%SRI-NIC.ARPA@VM.USC.EDU>
Sender: "(TCP-IP ARPA Discussions)" <TCPIP-L@VM.USC.EDU>
Comments: Warning -- original Sender: tag was Comments: Warning -- original Sender: tag was TCPIP-L@BYUADMIN
From: "C. Philip Wood" <cpw%sneezy%LANL.GOV@VM.USC.EDU>
Subject: MILNET/BBN IMP/ACC LH-DH/4.3BSD VAX Connection
To: Local BBoard - Postmaster <#TCP-IP@MVSA.USC.EDU>
Ever since new software was loaded on our MILNET Node '90' (BBN C-30)
December 3rd? we have been suffering from an inordinate amount of lost
"Rifnums" or to put it more succinctly Requests For New Messages from
our IMP. The high-level symptom is loss of connectivity. Currently,
the only solution is to call DCA and have them reset the IMP.
Does anyone know if this is a problem with the new software? A problem
with 4.3BSD UNIX imp/acc drivers? A simple configuration problem?
OR WHAT!
Facts:
VAX-11/785
26.0.0.90
ACC LH-DH/11 SN: 270, REV: C.4
ACC Cable (200')
BBN C30, PSN 7.0, Node: 90, Port: 0
Note the absence of an ECU.
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:44:55 GMT