Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!bionet!ames!excelan!keith From: keith@excelan.COM (Keith Brown) Newsgroups: comp.dcom.lans Subject: Re: Network Address NW386 & SFT 2.15 Keywords: netware386, routing, XNS Message-ID: <1528@excelan.COM> Date: 11 Jul 90 17:01:09 GMT References: <565@secola.Columbia.NCR.COM> Sender: news@excelan.COM Reply-To: keith@ca.excelan.com (Keith Brown) Distribution: comp Organization: Excelan, A Novell Co., San Jose, CA. Lines: 23 In article <565@secola.Columbia.NCR.COM> krupczak@secola.UUCP (Bobby Krupczak) writes: > >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! > *WRONG* .... The cables connected to a NetWare 386 server have IPX network numbers just like they have when connected to a NetWare 286 server. A good way of visualising the scenario with NW386 is that each 386 server contains a "virtual" IPX network. Pretend there is a cable inside your server and treat it using the same rules as the cables that physically hang out the back of the thing. Actually, there is only one rule. The IPX network number you assign to each cable must be unique on the IPX internet. Couldn't be simpler...... Keith ---------------------------------------------------------------------------- Keith Brown Phone: (408) 473 8308 Novell San Jose Development Centre Fax: (408) 433 0775 San Jose, California 95131 Net: keith@novell.COM ----------------------------------------------------------------------------