🚀 go-pugleaf

I am trying to get CAP going on my Sun SparcStation 1, running SunOS
4.1.2 -- can anyone help me get it going?  I know this is a long message,
but I wanted to be as complete as possible.  I would greatly appreciate
any responses!  (I accidentally posted this to comp.sys.mac.comm last
night.)

I have CAP 6.0 pl126 and apparently compiled it all properly.  We have a
GatorBox CS on the net too, and I have set all its settings to be
compatible with CAP.  I am trying to install CAP with Native Ethertalk
Phase II so it can get our ethernetted/unixed HPIIIsi to show up in the
Macs' Choosers so our phonenetted/appletalked Macs can print to them
easily.  I don't need papif or aufs since the Gatorbox takes care of
this.  As far as I can tell, I only need aarpd, atis, and lwsrv (do I
need snitch? in any case I'm not getting that far). 

The zone I want the printer to show up in (for now) is Duke.Ethernet. 
The problem is I can't seem to get CAP to know what it is and find our
GatorBox.  When I try to start things out from start-cap-servers with

	aarpd le0 Duke.Ethernet
	atis -l /var/log/atis.run
	atis debug debug debug

I get

	18:38:19 01/27/93  log file name /var/log/atis.run
	abInit: [ddp:   0.01, 72] starting
	18:38:20 01/27/93  Sent increment debug level signal to daemon[4225]
	18:38:20 01/27/93  Sent increment debug level signal to daemon[4225]
	18:38:20 01/27/93  Sent increment debug level signal to daemon[4225]

and if I do "atis -dn" I get

	debugging NBP
	abInit: [ddp:   0.01, 72], [GW:   0.01, 128] starting
	Reply num max for lkup reply is 5 (based on 104)
	NIS: NIS socket not available: error -1: Address already in use
	ECHO: ECHO socket not available: error -1: Address already in use
	RTMP: RTMP socket not available: error -1: Address already in use
	Couldn't establish nis, rtmp or echo socket, nothing to do

If I do "atistest" it gives me (last lines only)

	NBP SndNBP: sending
	NBP nbp_timeout: 4 tick timeout on -134219036, 0 remain
	nbp register error because: couldn't register name - is atis running?
	
even though it certainly is, though /var/log/atis.run is

        Reply num max for lkup reply is 5 (based on 104)
	NIS: NIS socket not available: error -1: Address already in use
	pid = 4225
	DEBUG LEVEL 1
	DEBUG LEVEL 2
	DEBUG LEVEL 3
        New default router 6.128, goodness 0->2
        Current default router 6.128, goodness 2
	Current default router 6.128, goodness 2
	...

Despite these problems, getzones works and atlook works.  Yes, /etc/services
has had the new UDP range for a long time now.  If I do "atis dump", the
/usr/tmp/nis.db file has 0 entries (it is just five lines of comments,
with the zone correctly noted).  The /etc/etalk.local file seems correct
with the exception of the bridge info:

	interface   	"le0"
	netRangeStart	 0.01
	netRangeEnd 	 0.10
	thisNet     	 0.01
	thisNode    	72
	thisZone    	"Duke.Ethernet"
	bridgeNet   	 0.06
	bridgeNode  	128
	bridgeIP    	127.0.0.1
	nisNet      	 0.01
	nisNode     	72
	asyncNet    	 0.00
	asyncZone   	""

This is despite the presence of /etc/atalk.local:

	# mynet		mynode		myzone 
	1		72 		Duke.Ethernet
	# bridgenet	bridgenode	bridgeIP
	19876		130		128.109.232.130
	
and the GatorBox setup with the same numbers.

If instead of the above aarpd call, if I turn on debugging with

	aarpd -D 20 -l /var/log/aarpd.errs le0 Duke.Ethernet

it prints

	20:14:26 01/27/93  log file name /var/log/aarpd.errs
	Interface le0, zone Duke.Ethernet, acquired node number 72/255.0

and hangs.  The log file reads

	New AARP mapping for node 231/0.1                   
	GetNetInfo reply packet arrived:                   
	  Flags 0x00, rangeStart 0001, rangeEnd 000a                     
	  Zone Duke.Ethernet (len 13), MCZAddr 9:0:7:0:0:7f                     
	Changing network range: 0000-fffe -> 0001-000a                   
	Probing for 72/0.1                   
	New AARP mapping for node 72/0.1                   
	etalk_resolve: node 72/0.1 try again later                   
	Got mapping for 123/0.1                   
	  Address: 2 60 8c 45 be 7a                   
	New AARP mapping for node 123/0.1                   

maps a bunch of other things, and keeps repeating
       
	Probing for 72/0.1                   
	etalk_resolve: node 72/0.1 try again later                   
	Probing for 72/0.1                   
	etalk_resolve: node 72/0.1 try again later 

until finally there's a 

	Adopting 72/0.1
	AARPD .... Running


So does anyone know what is going on here?  Why does it only half-work?
What do I need to do to get it to going?

And while I have your attention, let me ask two more quick questions:

1)  Instead of Duke.Ethernet, I would prefer for everything to be in
the Neuro.Ethernet zone.  This is a new zone (a week old).  Most of
the seed ports, mine included, broadcast that it is a valid zone, and
it shows up in the chooser.  However, when I refer to it in the GB,
the atalk.local, etalk.local files, and in the call to aarpd, I get
(from aarpd)

	Zone "Neuro.Ethernet" unknown, network default is "Duke.Ethernet"

Why can't I get this zone to work?

2)  How do I get the ProcSets files for lwsrv?

Thanks immensely to anyone who has made it this far!!


-- 
 ________________________________________________________________________
|   John      jfw@neuro.duke.edu          Duke University Medical Center |
| Whitehead   jfw@well.sf.ca.us           Department of Neurobiology     |
|________________________________________ Durham, North Carolina ________|