Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!swrinde!emory!hubcap!ncrcae!secola!krupczak
From: krupczak@secola.Columbia.NCR.COM (Bobby Krupczak)
Newsgroups: comp.dcom.lans
Subject: Re: Network Address NW386 & SFT 2.15
Summary: Me too!
Keywords: netware386, routing, XNS
Message-ID: <565@secola.Columbia.NCR.COM>
Date: 10 Jul 90 17:37:31 GMT
References: <jacksond.647498064@cica>
Reply-To: krupczak@secola.UUCP (Bobby Krupczak)
Distribution: comp
Organization: NCR Comten Columbia
Lines: 18

In article <jacksond.647498064@cica> jacksond@cica.cica.indiana.edu (Richard Jackson ) writes:
   paraphrase: Network number problems with NW386

I have encountered this "problem" too.  I phoned someone I know out
at Novell and they say this is a "feature".

Each NetWare 386 server requires its own unique network number!  In effect
each 386 NetWare server is a router also.

What novell has done is effectively redefined the network to not be the cable
running between the servers, but the servers themselves.  Imagine the 
nightmares this creates for real routing!

Your problem can be corrected if you number the 386 Server's internal network
number differently than the 2.1X servers.  The 386's internal router will then
route between the internal network number and the real 2.1X network number.

Bobby Krupczak