Configuring a default route for TCP/IP on a NetWare Server.

(Last modified: 16Jan2003)

This document (10013002) is provided subject to the disclaimer at the end of this document.

goal

How to Configure a TCPIP gateway on a NetWare Server

How to Configure a NetWare server to forward TCPIP to an internet router

fact

Novell NetWare 3.12

Novell NetWare 3.2

Novell TCPIP 4.x

Novell TCPIP 5.x

Novell NetWare 4.11

Novell NetWare 5.0

Formerly TID 2911404

Novell DHCP Server

symptom

No Default Route established

Cannot ping from the server past the router on a local segment

Workstation can ping all cards in the server but no devices on external segments

Cannot ping past Internet Router.

Cannot ping server from remote segments

Server cannot communicate to the internet

Server cannot ping internet

DHCP only handing out addresses on local segment - not to other Network segments

cause

For services like WEB Server, BorderManager, Proxy Server, VPN, NAT, SMTP, IPX/IP Gateway, IP/IP Gateway, LDAP Services for NDS, NWC etc. running on NetWare 4.x/5.x servers, the Default Route or Default Gateway must be configured on the NetWare 4.x/5.x server itself. If you are configuring a WAN dial-up connection with NIAS or MPR see "How to set up a default route to forward TCP/IP traffic over the WAN link"

fix

For NetWare 4.x/5.x servers it is recommended that the Default Route be configured in the INETCFG utility:

  1- LOAD INETCFG
  2-       Select> PROTOCOLS
  3-            Select> TCPIP
  4-                   Select> Static Routing
  5- Select> Enabled
  6-                     Select> Static Routing Table: <enter>
  7-                                     <insert> to bring up the Static Route Configuration
  8-                                                  Select> "Route to Network or Host" and <enter> to Bring up options
  9-                                                               Select> "Default Route" <enter>
10-                                                               Press down arrow key to "Next Hop Router on Route"
11-                                                               Enter ip address of the router.

12- Press the <Escape> key until you have exited INETCFG.
NOTE: "Save" or "Update" as directed.

13- Enter the console command "reinitialize system" to push the new default route onto the routing table.

NOTES: In the event that the new default route does not appear in the routing table, i.e., TCPCON does not show it, then you may need to down the server and bring it back up. If the server cannot be "downed", then you will need to unload TCPIP, and then perform a "reinitialize system." Many times, there are processes that are depending or running on TCPIP and therefore, TCPIP cannot be unloaded until these process are stopped or unloaded. The new default route will be placed in the routing table each time the server is started.

Once the default route is set up, you can verify it under the TCPCON utility. Load TCPCON and select IP Routing Table. Press <Enter> on Proceed. You should see an entry that looks like this:

Destination Next Hop Type Cost Interface
default 206.100.100.254 remote 1 <#>

NOTE: If the default route is not showing. then you can put a dynamic default route in the IP ROUTING TABLE. Remember that any routes placed in TCPCON are dynamically added and will be lost when the server is downed. This suggestion is primarily for those who cannot down the server until after hours but need the default rout to take effect immediately. The procedures are as follows:

1. LOAD TCPCON
    Select ---> IP ROUTING TABLE
        Select ---> PROCEED: <ENTER> WHEN DONE
            <INSERT> to bring up a new IP ROUTE INFORMATION table.

By default the destination will be default and mask of 0.0.0.0. Make the Next Hop you default router's IP address. This next part is critical. Change the Interface number to the same number as the NIC card on the router's segment. If this is not done, the route will not be added. The route will take effect immediately. Entering any route in TCPCON is not a solution, but rather TCPCON should be used as a diagnostic tool.

--------------------------------------------
For NetWare 3.12 servers, or 4.x servers using AUTOEXEC.NCF instead of INETCFG to configure cards / bindings:

    1- Edit the sys:etc\gateways file. Insert entry as follows:
           Net 0 Gateway <IP address> metric 1 passive <CR>
        NOTE: Where <IP address> is the address of the router/gateway to the rest of the Internet/network that you want to route IP to. Make sure that the sys:etc\gateways file is terminated with a Carriage Return.

    2- Create a \sys:\etc\NETINFO.CFG file with 2 lines-
        #!VERSION=2.3
        load IPCONFIG

3- Create the file sys:\system\TCPCFG.NLM (just an empty file).
NOTE: If the sys:\system\TCPCFG.NLM exists DO NOT create an empty file.

4- Reboot the server.

document

Document Title:	Configuring a default route for TCP/IP on a NetWare Server.
Document ID:	10013002
Solution ID:	4.0.5331023.2242471
Creation Date:	22Jul1999
Modified Date:	16Jan2003
Novell Product Class:	Beta Connectivity Products Groupware NetWare Novell BorderManager Services Novonyx

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.