🚀 go-pugleaf

	I need a little help in configuring our FastPath 4 (yes, something
of a fossil).

	The FastPath has 4.1 PROMs and currently running K-STAR 9.1.

	We will be running CAP6.0 pl125 (pl60 or so is running now).  Since
all six of our Macs (locally) are on Ethernet it's configured as native
EtherTalk.  We need the FastPath (since it's already available to us)
to link a few LocalTalk printers to our happy EtherTalk network.  We also
tried Apple's Internet Router as an iterim solution but that had it's own
set of problems.

	We have two particular problems:  one is that for ONE Mac on the
network, the VersaTerm Telnet Tool complains that "MacTCP did not open
successfully."  There are two other curious messages:

%	If MacTCP is using either LocalTalk or EtherTalk with a "router"
	(FastPath, GatorBox, etc.), make sure your address IS in the MacIP
	range of the router.
%	If MacTCP is using Ethernet, and a "router" exists on the network, make
	sure your address is NOT in the MacIP range of the router.

	What is it talking about?  Turning off the FastPath immediately
clears up the problem.  Could it be there aren't enough Static IP Clients
assigned (currently 20 vs 40 dynamic)?  Each Mac (static, because each has
their own IP address, correct?) is generating four or more Entities (6Mac *
4Entity > 20Static).

	The other problem is that the rest of the IP network seems to get
screwed up.  A few Unix servers disappeared then reapeared after the box was
turned off.  Coincidence?

	Otherwise the Box seems to work.  :-/


	Now a few questions (that may or may not relate to our problems):

	What do I do with the IPTalk Interface configuration?  When I talked
to Shiva Tech support the guy said I don't need it.  So I cleared the IPTalk
entries using the FastPath Manager which defaulted to AT Zone "*" and AT Net
Number 0.  Is it now disabled?

	After studying the docs for CAP, KIP, atalkab, and the Kinetics (yes,
Kinetics) manual, I think I see why IPTalk isn't needed -- EtherTalk works
fine on its own.  But could IPTalk become useful for communicating to another
Box on the otherside of our IP Gateway?  Could this be layered on top of
everything else we set up?

	Could our problems be caused by a conflict between the Box and the CAP
server?  Must the settings in atalk.local jive with the Box's settings?

	Next, should we install atalkad?  Would it ensure that the IPTalk
network stays dormant under K-STAR?  Should we use KIP?  As far as I can
tell, all it does is take the functions of K-STAR and and the FastPath
Manager and puts in on a Unix host -- in en even less documented fashion
(for me, anyway).  But K-STAR supposedly works fine with atalkad.

	Anticipating installing atalkad, I downloaded a copy of MGConfig 2.09
to produce an atalkatab file.  An iteresting experience.  There were a few
entries that I'm not sure about.

*	Serial number.  Does this matter?

*	Ethernet IP Net Number on the IP Mask and Address card.  Is this just
	to verify that the proper subnet mask is set?


	That's all I can think of for now.

Thanks,

	joe piazza


--- "If you prick me, do I not leak?"  Data

CS Dept. SUNY at Buffalo 14260
jmpiazza@cs.Buffalo.edu		jmpiazza@sunybcs.BITNET