Discussion Locked

NetWare IP Server

0 helpful
19 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a NW 4.11 server, which is working fine with IPX on the local subnet. Now I want to add TCP/IP for clients on other subnets to attach to this server. I have researched Novell's site, and find their info very confusing. I have never done this before, and need a step by step layout.

19 replies

by fgarber

I don't understand why you would want to run ip on a Novell server but I would suggest you upgrade to Netware 5 if you must run ip on novell. There are much better solutions to integrating Novell servers into an ip network than to try running ip onany novell box prior to release 5.

by edpcs

Upgrading to NW5 is not an alternative at this time. What are the "better solutions" you referred to?

by fgarber

Use IPX routing. You can route IPX on most if not all routers. Some may charge a small amount for the software. Cisco charges $140.00 for the upgrade. We keep out novell servers separate from the ip side for security reasons but still make the internet access and novell access available to all our users by routing through a Cisco router. In some remote sites we use Webramps to provide access to the internet while keeping ipx traffic strictly separate.

by gnet158

I think you want to add TCP/IP on your Netware server. Do the following at the server console

Load TCPIP
LOAD (NETWORK CARD) SLOT=(SLOT #) FRAME=ETHERNET_II NAME=(NAME OF NIC CARD)

BIND IP (NETWORK CARD) ADDR=(IP ADDRESS FOR SERVER) MASK=(SUBNET MASK) GATE=(GATEWAY ADDRESS)

That's it. Novell is a very strong product and I can't think of anything better than NDS. Good luck.

by timber

I would suggest sticking with IPX if at all possible such as fgarber@hansonpipe.com suggestion. I have seen several companies try to load IP on a netware 4.11 server and it cause severe problems. I ran IP on a small netware network and ran into a lot of connectivity issues that Novell wouldn't help me with.....

However it is possible as suggested by gnet158@hotmail.com but I would procede very catiously if that's what you choose to do.

by estebandelatorre

Let?s use the GUI interface!
0.- Make a copy of autoexec.ncf!!!
1.- Load inetcfg.nlm (if it's your first time, answer yes to transfer!)
2.- Select Protocol, then TCP/IP and Just enable it! no more config needed here, but you can browse the available options, just to take a look.
3.- Let's Bind: Select Bindings, TCP, fill in your IP address (e.g.: 129.11.43.123) and your mask (under the format FF.FF.0.0 for a "B" class)
4.- Select Expert TCP/IP options, frame type should be ETHERNET_II.
Nofurther config needed.
5.- Reinitalize system

Take a look at autoexec.ncf, you can see lines begining with #, that?s inetcfg's finger. From here and then, make every modification from inetcfg.

Test your work.
Issue a ping from a client with ip installed and working in the same subnet.

by kevin anderson

posters 5 & 3 both have the correct answers. Either will work, they do the same thing through two different methods.

You will not have any problems with IP on a Novell Server. It will work fine. Routing is the same as for any other IP routing. Make sure the subnets are different, and you're set. I agree that if you're just starting with IP, you will find it easiest to run both for a while, and once you have a good DHCP solution in place, then slowly phase out IPX IF NECCESSARY. As longas you don't have a huge network, run them both. It won't make an appreciable difference.

When you do get rid of IPX, the biggest problem for you will be with Print Servers. Check that they support it first.

Kev.

by jcrowe

I agree with answer from 6, however I'm confused about you motivation for TCPIP.

If your users in other subnets cannot see your 4.11 server with IPX now, adding TCPIP won't help.

4.11 (to best of my knowledge) cannot run in pure TCPIP mode - all authenticated connections will be made via IPX, and all services advertised by the server will be via IPX.

Don't get me wrong, its worth doing, we had two 4.11 servers covering 4 subnets and up to 500 simultaneous connections - it works great ... but to move to a pure IP network, we upgraded to 5.1 (which is REALLY cool!)

by david.pennington

You don't want to do this. Novell print servers and print queque's don't want to work, unless you upgrade to at least version 5 with NDPS printing. Keep in mind that your printers still run in bindery/NDS mode.
You also loose some command line functionality. Some of the Novell commands and utilities must have IPX loaded to work.

by fxh

We also had this situation. Enabling TCP/IP as a protocol at the server is only step one!
To give client WS access to NW server through IP, you have to install NetWare/IP add on (comes witin 4.11 for free) on the server. Understanding NW/IP conceptis a little bit difficult, but there is a very good step-by-step manual published by Novell. You can find it in the AppNotes (July 1997): "Installing the First NetWare/IP Server". Take a look at:
developer.novell.com/research/appnotes/1997/a9707.htm
It?s nearly fool proof!
Good Luck.

This discussion is closed to new replies.