Discussion Locked

NetWare 5.1:Moving to IP only across WAN

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Our organisation is upgrading all major network links across the WAN. Once this is complete IPX traffic will not be allowed to travel across the WAN. Server to server (building to building) communications will be via IP only. IPX traffic will still be allowed within the individual buildings but cannot travel outside the building.

What I want to know is what impact will this have on Server to server communications and clients logging into remote servers? Is there anything that needs to be done before IPX is taken off the WAN?

Our network consists of NetWare 5.1 servers configured with IP and IPX. Clients are Windows 98 (soon to be Win 2000) with Novell client (again IP and IPX) 3.20 (minimum) installed.

Thanks for any help...

6 replies

by jimbb

Hi Chris,
It depends a bit, but most likely you should consider SLP. With IPX you rely a lot on SAP broadcasts to "find" your services. A client comes on and asks the world if there is a NetWare server somewhere (Get Nearest Server), and every NWserver will reply (give nearest server) saying "Me!". In most cases your client will log on to the first one that replies.

In an IP only WAN/LAN without broadcasts this is different. You need to have some box on every "broadcast domain" collecting info about the services there, and exchange that info with a similar box in other LANs. This is where SLP (Service Location Protocol) comes in.
Per segment you need to set up an "SLPDA" (SLP Directory Agent). This agent will collect all the information, store it in NDS, and communicate it to other SLPDAs. You can configure to which it will talk, by putting their IP addresses in SYS:\etc\slp.cfg. The other servers in the same segment should have the IP address of "their" SLPDA in the samefile, that way they will give info like "I have ARCserve and I can run RConsole, and I have a replica of partition XYZ".
This way at least the servers are aware of each other, and NDS sync can run without any problem.

(reached the limit it seems)

by jimbb

(the rest)

If you want the clients to allow access to services "across the WAN", you'll need to configure the "Service Location" tab. At least the IP address of the SLPDA on their segment is required. Should you configure IP only, your clientwill then ask the SLPDA "I need to log in onto server ABC, please give me its IP address".

You can run this parallel with IPX, to test if the serves communicate properly. For example, check in NDS if the IP services are really stored. Type "Display SLP DA" to see if the servers know who to talk to, and sonsider it "up". Type "display slp services" to see what the server has discovered or received from the DA. Type c:\novell\client32\slpinfo to see if a client talks to the proper DA, and considers it "up".

There's a lot to say about this, more than 1930 characters, but on support.novell.com you'll find excellent documentation explaining what SLP is and how to set it up.

Jim

by gareth chapman

If using client32, edit the NWHOST file usually found on c:\novell\client32\nwhost and add the name of the tree and it's ip address, and a second line for the servername and it's ip address. I have 300+ win95/98 PC's connecting to our NW5.0 server across "IP only" (No ipx, NO saps) wan links.

This discussion is closed to new replies.