Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!maths.qmw.ac.uk!dhb
From: dhb@maths.qmw.ac.uk (David Burgess)
Newsgroups: comp.protocols.appletalk
Subject: RE: problem with CAP6.0 -- bogus node
Message-ID: <2127.9106101534@ariel.maths.qmw.ac.uk>
Date: 10 Jun 91 15:34:11 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 28

Jude George (jude@nas.nasa.gov) writes:

----- Begin Included Message -----
[...]

I am having a rather bizarre problem with CAP.  No matter what machine I run
it on, the server programs always think they are on node 57.  I've compiled
the software on two Sun 4's and one SGI Iris, alternately using IPTalk and
"native" Ethertalk (the latter only on the Suns).  I get identical results
each time.  None of the machines have 57 as the last byte of their IP address.

[...]

----- End Included Message -----

I had a similar problem  where aarpd came back with node number 213 all
the time. Situation: CAP6.0, not many of patches applied, Sparc2, native
ethertalk, no bridges anywhere.

Using the Sun etherfind (on another machine) I came to the conclusion
that the CAP sun wasn't putting out any appletalk packets when aarpd was
run. But I could set up lwsvr, and this was seen by Macs.

Ok, so this isn't a solution, it's another problem. (Sorry World.)
But maybe the problems are related.

David Burgess
Astronomy Unit, Queen Mary and Westfield College, London.