Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!elbereth.rutgers.edu!hobson From: hobson@elbereth.rutgers.edu (Kevin Hobson) Newsgroups: comp.dcom.lans Subject: Re: Network Address NW386 & SFT 2.15 Keywords: netware386 Message-ID: Date: 9 Jul 90 14:37:12 GMT References: Distribution: comp Organization: CCIS Telecommunications Lines: 53 To: jacksond@cica.cica.indiana.edu In article jacksond@cica.cica.indiana.edu (Richard Jackson ) writes: > Currently have 1 file server online using Netware SFT 2.15. Adding 2 more > using Netware 386. Have in fact had 2nd server up and running at same time > as SFT2.15 but am getting routing errors. > > 2.15 server is network address 00000001. > > 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). However I cannot then make the cable address this number. > So I give it a different address causing routing errors. I also tried > setting the internal (or node/ipx) address to 00000002 and the cable address > to 00000001. This also causes routing errors. (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. > 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...) > > When I try and make the internal and cable addresses the same on the NW386 > server I get an error message saying that there is already a network running > with that address and it will not let me continue till I use a different > number. You have to number the internal before the cable address also. > Well, Novell 386 has changed the idea of network numbers (hex representation). Under Netware 2.15, the external network number was the network number for both the server and network. Under Novell 386, in addition to external network number, servers have a internal network number. And this number must be different for every server. Read the Novell Concepts book for more information. Since we at university are base on IP subnetting, we have base novell network numbers scheme on the following confusing method: IP network: 128.6.20.0 Novell external network (works under 2.15): 80061400 Novell internal network (and addition servers): server1-80061401, server2-80061402, server3-80061403, etc. The hex representation external network number is used by nodes on the network. The reason we pick this scheme had to do with us using Cisco "show novell servers" and "debug novell-routing" commands. If novell was not using variation of XNS, it would be a lot easy to use decimal representation. -- Kevin Hobson Internet: hobson@rutgers.edu Rutgers - The State University UUCP: {backbone}!rutgers!hobson P.O. Box 879, CCIS, Hill Center, Busch BITNET: hobson@{cancer,pisces}.BITNET Piscataway, N.J. 08855-0879 PHONE: (908) 932-4780