From: cranch@novell.com (Christopher Ranch)
Subject: Re: Novell & network numbers
Followup-To: comp.sys.mac.comm
Organization: Novell Inc., San Jose, Califonia
Date: Fri, 14 Aug 1992 22:30:28 GMT

In article <l8o9grINN38p@alshain.usc.edu> lkimes@alshain.usc.edu (Lance 'Moof' Kimes) writes:
>
>	I don't directly control the novell server, but I am responsible for
>	the Ethernet backbone to which it connects.  The localtalk net is 
>	strictly internal to their dept. & not connected to my network(except
>	that we both have access to their server).  

	The LocalTalk net will be connected to your Ethernet through the
	router.  Your (words in parens) confirms that you are indeed routing.

>	Before we switch to
>	Phase 2, the servers network number was the same as the rest of the 
>	network, after they upgraded to netware 3 & us to Phase 2, their 
>	network number changed to 7261. 

	Ok, I'm not sure about NetWare 2.x servers, but I think they would
	allow you to bind the AppleShare VAP service to the interface.  For
	NetWare 3.x, the AppleTalk stuff was ported to the NLM architecture.
	In this architecture, you only were able to have services visible
	on the internal net, not an actual physical interface.  (This may
	change, but this is how it works today.)  The folks who ARE in
	control of the server have the following line in their AUTOEXEC.NCF
	file:

		load appletlk net=7261 zone = {"Ethernet"}

>	As you know, Phase 2 separates 
>	network numbers and zones from meaning anything in relation to 
>	each other and that an extend network can be composed of one zone 
>	combining two logical networks.

	One minor nit about the above: one zone name being associated with
	lots of [physical] networks, and discontiguous ones to boot, is
	NOT NEW to Phase 2 or extended nets.  Or were you trying to say
	that a single zone name can refer to each network in a physical
	cable's network range?

>	We want to keep the network numbers the same for the moment. 

	Sorry, but you CAN'T.

>	I don't know what there internal or localtalk network numbers are. 

	The internal numebr is 7261.  I can't tell what the LocalTalk's
	number is either, from the data you've presented.

>	I do know that their external ethernet number is not what we want 
>	it to be. 

	Just by the fact that you can see the server proves that your
	external Ethernet is configured correctly.  If it wasn't, you
	couldn't see it.  Period.  The AFPServer can only possibly exist
	on the internal net.  Period.  (At least today ;).

>	If I use interpol to scan the network, it returns something 
>	like this:
>
>	Net	Node	Name		Type		Zone
>	644	35	seawolf		AFPServer	Ethernet
>	644	35	seawolf		Macintosh IIci	Ethernet
>	644	79	bill		Public Folder	Ethernet
>	7261	1	ACCOUNTING	AFPServer	Ethernet

	Right.

>	It realizes its on an extended network and create its own logical 
>	network and network number and places itself in the zone "Ethernet".

	No.  The NetWare administrator set up the internal, logical network
	and associated it with the zone "Ethernet".  Then when they load
	AFP, it binds to the internal net.  It doesn't touch the external
	net, whether or not it's extended.

>	We will soon begin routing and creating the new logical networks upon we
>	will route traffic across our backbone. If every novell server has to be
>	allowed its own logical, external network, it will be difficult to 
>	smoothly manage routing.

	Given the above wording, I'm not sure what you're saying.  Every 
	Novell server has an internal logical network that the services
	live on.  Phase 1 to Phase 2 migrations are a bitch, if that's
	what you're saying.  How will this impede on router management?
	It's just another network...

>	You mentioned an appletalkcf(config I prosume) file, are they doing it
>	wrong and have can I fix it?
>
>Lance Kimes

	It doesn't look like there's anything wrong with the autoexec.ncf
	file, just your understanding of how AppleTalk and NetWare works.

	I hope this helps.  Ask again if I appear to be a bone head.

	Chris
---
Chris Ranch
Internetworking Products Division
Novell, Inc.  San Jose, CA
(408)473-8667  cranch@novell.com
Newsgroups: comp.sys.mac.comm