Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!CUNIXC.COLUMBIA.EDU!cck
From: cck@CUNIXC.COLUMBIA.EDU (Charlie C. Kim)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP problems
Message-ID: <8801240718.AA06279@columbia.edu>
Date: 24 Jan 88 07:18:40 GMT
References: <8105@reed.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19

The problem with registering names (e.g. atistest failure) comes about
because you have an extra line in your atalk.local.  There is an
undocumented feature: you can specify the appletalk address of a host
that will handle name registry.  This is done by adding a third
(valid) line that contains an appletalk network and node number....

The main reason this was done was to allow me to test server programs
on machines that I didn't have root access to.  (It could be of use to
allow machine to register in different zones, etc if the tickle
protocol documented in nbp.ext was implemented).

pinger doesn't gets "no response" because, to date, very few machines
implement the AppleTalk echo protocol.  CAP hosts running atis and
AppleShare servers will return echo packets.  The next release of KIP
should implement it also.

Charlie C. Kim
User Services
Columbia Unviersity