Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!bu-cs!att!mcdchg!amtfocus!troym
From: troym@amtfocus.UUCP (Troy Monaghen )
Newsgroups: comp.protocols.appletalk
Subject: Re: Problem with K-Star replacing KIP
Message-ID: <177@amtfocus.UUCP>
Date: 22 May 89 14:28:01 GMT
References: <27890@cornell.UUCP>
Reply-To: troym@amtfocus.UUCP (Troy Monaghen (Software))
Distribution: comp
Organization: Motorola Inc. GSG/AMT, Schaumburg, Illinois
Lines: 19


I had what I think is a similar problem when I first set up my FastPath.  My
unix machine does not currently support kip so I had to start out with K-STAR.
I spent several days playing with various combinations of Appletalk Zone
and address names in the K-STAR configuration, but all I could see with
atlook was the IPADDRESS reply from the FastPath.  It turned out that every
configuration I tried had the LocalTalk and Ethernet AppleTalk Net Number
the same.  As soon as I made them different... voila!  All of a sudden
all of my AppleTalk entities appeared and everything worked from then on!
So my current working configuration has 3 different Appletalk net numbers
(one for LocalTalk, one for Ethernet, and one for UDP).  Since I am relatively 
new to the appletalk world, I don't really know what constraints there are to 
AppleTalk Net's and Zones, and in the three or four time I went searching 
through the Kinetics Manual I did not see any guidelines.  Does anybody know
of any guidelines for AppleTalk net numbers and FastPath's?

-- 
Troy Monaghen, Motorola, Inc.			 chg.mcd.mot.com!amtfocus!troym
General Systems Group - AMT			    uunet!harper!amtfocus!troym