Install TCP/IP Services on Novell NetWare Servers

Reviewed: September 3, 1997
Revised: September 3, 1997

Prerequisites

NetWare 3.12 Installation Steps

Example for Ethernet Adapter Card

Example for Token Ring Adaptor Card

NetWare 4.1 Installation Steps

References

Created for TECHNIC Network Builder

Purpose

To provide a step by step installation guide for installing the TCP/IP communication protocol stacks (programs) on a Novell NetWare server. 

TCP/IP is needed for various Internet services running on a Novell Netware server such as a www, ftp, gopher, email, etc., and for routing IP on Netware. If your server is not also running one of these services, you do not need TCP/IP on your server. 

TCP/IP on NetWare is supported through a suite of programs called NetWare TCP/IP, which includes the following NetWare NLM (Netware Loadable Modules) program files: 

1. NetWare TCP/IP NLM (TCPIP.NLM) 

 
2. Simple Network Management Protocol NLM (SNMP.NLM)

 
3. SNMP event logger NLM (SNMPLOG.NLMM)

 
4. TCP/IP Console NLM (TCPCON.NLM) 

 
5. IP Configuration NLM (IPCONFIG.NLM)

 
6. IPX /IP Tunnel module (IPTUNNEL.NLM)

 
7. Sample Internet database files (GATEWAYS, HOSTS, NETWORKS, PROTOCOL and SERVICES) 

Prerequisites

Before installing the TCP/IP components for NetWare, your computer systems must meet the following requirements: 

1. A 386/486 PC system running netware 3.12 or later version. 

 
2. Minimum of 12MB memory; 16MB is recommended to run efficiently. 

 
3. A network adapter card (Ethernet, Token Ring, ARCnet or FDDI) and the corresponding LAN drivers must be installed in the computer. 

 
4. The LAN drivers must be certified for supporting Netware 3.12 or later. Some LAN drivers support the IPX protocol (Netware default protocol) but do not support TCP/IP. Check with your vendor for the correct LAN network adapter card and drivers for TCP/IP support. 

NetWare 3.12 Installation Steps

Installing the TCP/IP modules on a NetWare 3.12 server involves three basic steps: 

1. Loading the TCP/IP NLM 

 
2. Loading the LAN drivers to support TCP/IP 

 
3. Binding IP to LAN Drivers 

At the file server console prompt, type load TCPIP. 

Loading the TCPIP.NLM program also supports several command-line options (for more information read the Netware TCP/IP Transport Supervisor's Guide). One of the most frequently used options is: 

load TCPIP forward=yes

If the option forward=yes is used, the NetWare server will act as a routing device on your network (see Routing IP on Novell Server). 

Loading the LAN drivers to support TCP/IP

The next step is to load a network driver that handles Ethernet_II frames (for Ethernet network) or Token-Ring_SNAP frames (for Token Ring network) for the TCPIP protocol. NetWare usually uses the Ethernet_802.3 frame (Ethernet network) or Token-Ring frame (Token Ring network) as the first frame to support IPX protocol (Netware's default protocol). Therefore, the same driver has to be loaded a second time to support a different frame (i.e. Ethernet_II or Token-Ring_SNAP). Assuming you have a Novell NE2000 network adapter card installed on your file server on port 300, using IRQ 10 you would issue the command: 

;modify the following line to reflect your network card's port and interupt.
LOAD NE2000 port=300 int=10 frame=Ethernet_II name=IPnet 
(Ethernet) 

Or an IBM Token Ring card (IBMENIO) with port 280, using IRQ 11: 

LOAD IBMENIO port=280 int=11 frame=Token-Ring_SNAP name=IPnet 
(Token Ring) 

Note: Because Ethernet_II or Token-Ring_SNAP is usually the second frame to be loaded after the Ethernet_802.3 or Token-Ring frame, NetWare will report that the "previously loaded driver was used re-entrantly". This is a normal message. 

Binding IP to LAN Drivers

To bind the IP protocol stacks to your LAN drivers, you need to know three sets of IP addresses for your network: 

• IP address of your server 

 
• Network Mask 

 
• The default router/gateway address 

Bind IP to IPnet addr=204.184.10.1 mask=255.255.255.0 gate=204.184.10.254 

After the command has been entered, TCP/IP should be running on your NetWare server. 

Automating the Processing of Loading Drivers

To automate the process of loading TCP/IP drivers on your NetWare server, you should put the commands listed above in the AUTOEXEC.NCF file located in SYS:SYSTEM directory. You must be logged into the server as a user who has write privileges to make changes to this file. 

Example: SYS:\SYSTEM\AUTOEXEC.NCF for Ethernet Adapter Card 

; 
; Load and Bind TCPIP modules 
; 
load TCPIP 
load NE2000 port=300 int=10 frame=Ethernet_II name=IPnet 
bind ip to IPnet address=204.184.10.1 mask=255.255.255.0 gate=204.184.10.254

Example: SYS:\SYSTEM\AUTOEXEC.NCF for Token Ring Adapter Card 

; 
; Load and Bind TCPIP modules 
; 
load TCPIP 
load TOKEN frame=Token-Ring_SNAP name=IPtoken 
bind ip to IPtoken address=204.184.10.1 mask=255.255.255.0 gate=204.184.10.254

NetWare 4.1 Installation Steps

Installing the TCP/IP modules on a NetWare 4.1 server involves two basic steps: 

1. Loading the TCP/IP NLM 

 
2. Loading the LAN drivers to support TCP/IP and restarting the server. 

1. At the file server console prompt, type load INETCFG. 

 
2. Next, select Protocols option. 

 
3. Select TCP/IP and press ENTER to enable. 

 
4. Enable IP Packet Forwarding (only if you have TWO or more Network Interface Cards). 
5. Enable RIP and Static Routing. 

 
6. Enter the Gateway/Router's IP address in the Static Routing Table as Default Route. 

Next load a network driver that handles Ethernet_II frames (for Ethernet network) or Token-Ring_SNAP frames (for Token Ring network) for the TCPIP protocol. NetWare usually uses the Ethernet_802.3 frame (Ethernet network) or Token-Ring frame (Token Ring network) as the first frame to support IPX protocol (Netware's default protocol). Therefore, the same driver has to be loaded a second time to support a different frame (ie. Ethernet_II or Token-Ring_SNAP). 

1. Load INETCFG and select Bindings option. 

 
2. Press INSERT, select TCPIP, and select the board to support IP. 

 
3. Enter IP Address, Subnet Mask and save the configuration by pressing ESC. 

 
4. Finally, close down the fileserver and reboot it.

References

Hunt, Craig. Networking Personal Computers with TCP/IP. O'Reilly and Associates.

Hunt, Craig. TCP/IP Network Administration. O'Reilly and Associates.

TCP/IP Transport Supervisor's Guide. Part 100-001866-001.Novell Publishing.