change purt TCI/IP on Netware 5.0

[ikendo]

Hi guys,

This is kind of newbie queston as you can see im not a Netware gurus. I enter this company and they still using Netware 5.0 and within next few weeks we going roll over to Windows 2000. We want to keep the Netware as a file server only and we want to change ipx/spx to pure TCP/IP. Whats the steps need to involed?.

thanks

 

[Provogeek]

First in INETCFG enable the TCP/IP protocol under the PROTOCOLS menu item. Be sure to change to an End Node unless you do plan on routing. Be sure to provide a default gateway under routing options, you can also give the server DNS info if it needs it.

Second in INETCFG you need to BIND IP to the NIC, this will be under the BINDINGS menu item. In this menu press INSERT and choose your IP protocol, then choose your NIC. Give the system an IP address and subnet mask and save all info. Reinitialize the server or bounce it. Your IP will be up and running, and users will be able to login via TCP/IP

Third you want to setup SLP. If it is a small single Netware server with under 50 users, just execute SLPDA and let it do the defaults and be sure to add the LOAD SLPDA to your AUTOEXEC.NCF If your network is more than a single server and/or you have more than 50 users and/or you have more than one location then you will want to read up some on SLP to set it up. NTS has some good TIDs that give you how to instructions. Or you can just hire a consulting partner to do it for you. There are also SET commands and SLP.CFG setup if you go this route.

Fourth you want to figure out how to distribute SLP information (SLP is to TCP what SAP is to IPX). If you use a NetWare DHCP server in 5.0, then just add options 78 and 79, providing DA and scope information. You can also set these options with a Win2K DHCP. You however can not do this with an NT4.0 DHCP. The DA will be the IP address of your server. The scope will be UNKNOWN (having a brain fart right now so I could be wrong on the default scope name). You can also set this information staticly in the client properties; or you can just let the system multicast (causes network traffic).

This should give you a basic setup to acomplish what you want. You may want to look into eDirectory 8.6 if you will be using both NOS's. Then you will be able to manage security for both servers from a single database. Brent Schmidt CNE, Network +
Senior Network Engineer

Why do user go into a panic when a NetWare server goes down, but accept it as normal when a Windows server goes down?

 

[ikendo]

Woa! thanks for the steps.

 

[fitzdr]

Don't forget to set the client protocol bindings to use TCP/IP only. If its not available on the client you may have to reinstall and select to use TCP/IP.

Also check to see if you have any programs that require IPX. We a couple of these programs but were able to upgrade them to a TCP/IP version.

Check the following link, there is a paper on migrating to pure IP in Netware.

http://www.tinypineapple.com/luddite/beigepapers/

There are also links to several AppNotes that provide greater detail.