jacksond@cica.cica.indiana.edu (Richard Jackson ) (07/09/90)
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. Any suggestions/comments/shared experiences would be helpful and appreciated. Richard jacksond@cica.cica.indiana.edu ------------------------------------------------------------------------------- Disclaimer: No one but me. Voice: (812)331-6412 (8am-5pm Indiana Time) Quote: "The smallest deed done is greater than the grandest of intentions"-Anon -------------------------------------------------------------------------------
hobson@elbereth.rutgers.edu (Kevin Hobson) (07/09/90)
In article <jacksond.647498064@cica> 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
donp@na.excelan.com (don provan) (07/10/90)
In article <jacksond.647498064@cica> 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
krupczak@secola.Columbia.NCR.COM (Bobby Krupczak) (07/11/90)
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 Krupczakkeith@excelan.COM (Keith Brown) (07/12/90)
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 ----------------------------------------------------------------------------