Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!ames!excelan!donp From: donp@na.excelan.com (don provan) Newsgroups: comp.dcom.lans Subject: Re: Network Address NW386 & SFT 2.15 Keywords: netware386 Message-ID: <1515@excelan.COM> Date: 9 Jul 90 17:07:12 GMT References: Sender: news@excelan.COM Reply-To: donp@novell.com (don provan) Distribution: comp Organization: Novell, Inc., San Jose, California Lines: 38 In article jacksond@cica.cica.indiana.edu (Richard Jackson ) writes: >I understand that when servers are connected to the same backbone (thin net >in this case) they have to have the same address. So when loading in my >lan driver I set the internal network address for the NW386 server to the >same (00000001). As Kevin Hobson correctly points out, this is incorrect. NetWare 386 servers have a virtual network internal to the IPX code. This network requires a network number different than *all* other network numbers, including both virtual *and* physical networks, in the connected IPX internet. >I also tried >setting the internal (or node/ipx) address to 00000002 and the cable address >to 00000001. This also causes routing errors. This should have worked, unless you set the internal network address to 00000002 on more than one NetWare 386 system. Perhaps if you were more specific about what these "routing errors" were.... > (Netware386 does use 2 network >address BTW. The ipx/internal/node address when binding the lan driver and >a "cable" address which I took to be the external or network address the other >file servers would see. This is correct. The network number on the bind command line is the external network number. All servers connected to that network must agree on the same network number. >When both servers are up I can login (have to both) but one does not recognise >the other. I cannot ATTACH to the other also (of course...) This is a symptom of two servers having different external network numbers for the same physical network. I expect you are also seeing lots of jabbering on the NetWare 386 console about network address conflicts. don provan donp@novell.com