If you have servers that use TCPIP, you will need to verify that the proper default route is configured. This is vital if you wish to have these servers communicate properly to other networks both on and off campus via TCP/IP.

Included in this document are instructions for configuring NetWare 4 and 5 servers for a default route. If you are unsure of what your default route should be, you can refer to http://fmpro.umnet.umich.edu/umnet/nicrinfo/.

Configuring NetWare 4.x,  5.x, and 6.x default route.

Using Inetcfg:

If your LAN drivers and protocol bindings are configured through inetcfg, the following steps will guide you through adding the default route.

At the server console type, "load inetcfg" and press enter.

Note: If you receive a prompt asking you to "transfer of LAN drivers, protocol and remote access commands from AUTOEXEC.NCF," choose No, exit inetcfg, and follow the instruction for "Using Autoexec.ncf:"

Choose Protocols, then TCP/IP. Make sure Static Routing is enabled and highlight "Select from list" next to "Static Routing Table" and press Enter.

Press Insert and then press Enter on "Route to Network or Host" and choose "Default Route."

Press Enter on "Next Hop Router on Route:" and type the address of your default route (or gateway.)

Press "Esc" twice and choose "Yes" to "Update Database." Press "Esc" again and choose "Yes" to "Update TCP/IP Configuration?"

Using Autoexec.ncf

If you are loading your LAN drivers and protocol bindings using the Autoexec.ncf file instead of inetcfg, you will need to add the GATE= setting for each instance of a BIND IP line.

For Example: BIND IP TO 3C905 ADDR=141.211.x.x MASK=255.255.255.0 GATE=141.211.x.x