Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!ucsd!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  rgyd taking over the machine
Message-ID: <9008221401.AA19733@richter.mit.edu>
Date: 22 Aug 90 14:01:54 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 15

Yup, I've seen this before. The most usual cause was a broken, wedged, or outright
dead /etc/tcpd. Trying using /etc/ping to check if TCP/IP to the node is working.
If it is, then try using "telnet" or "rlogin" to make certain that you're getting
to the *correct* machine (we had, at one point, a machine with a screwed up host
table that kept stealing packets meant for the machine with the rgyd). Both
registry and printing services use NCS for communications, which in turn uses TCP
services.


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)