Networking

Configuring TCP/IP on your NetWare server for Internet access

John Sheesley outlines the changes that you'll need to make in order to allow your NetWare server to route TCP/IP to the Internet.

Have you loaded TCP/IP on your NetWare server and connected your network to the Internet? Have you also had problems pinging your NetWare server from the Internet or making Internet applications on your NetWare server available outside of your internal network? If so, you may not have configured your TCP/IP stack properly. In this article, we’ll show you the changes you need to make in order to allow your NetWare server to route TCP/IP to the Internet.

Following proper protocol
As you know, both NetWare 3.x and 4.x use IPX as their default protocols. NetWare 5 can use either IP or IPX as its default protocol. However, if you want the default protocol that you run on your server to be accessible on the Internet, then you must install TCP/IP.
In this article, we won’t go into detail about how you install and bind TCP/IP on your NetWare server. You’ve probably already done that. If you haven’t, it’s not much harder than binding IPX. What we’re concerned with here are the pitfalls that you should avoid while connecting to the Internet.
Installing TCP/IP on your NetWare server isn’t extremely difficult. However, if you want it to communicate properly on the Internet, you’ll have to jump through a few more hoops. The easiest way to configure TCP/IP for the Internet is to use your server’s Internetworking Configuration utility (also known as Inetcfg).

Inetcfg is an NLM that runs on your NetWare server. You can launch it either directly from your server’s console or from your workstation by using Rconsole. To start Inetcfg, type load inetcfg and press [Enter] at the server’s console prompt.

If you’ve never used Inetcfg before, it will prompt you to move LAN driver, protocol, and remote access information from your AUTOEXEC.NCF to Inetcfg’s configuration files. Select Yes and press [Enter] to transfer the information and to continue using Inetcfg. In the future, if you want to make any modifications to network card or protocol settings, you’ll need to use Inetcfg.

After the Internetworking Configuration menu appears, select Protocols and press [Enter]. You’ll see the Protocol Configuration menu appear. Select TCP/IP and press [Enter]. Then, the TCP/IP Protocol Configuration menu appears.

To configure TCP/IP to be viewable from outside your network, highlight IP Packet Forwarding and press [Enter]. Then, select Enabled (“Router”) and press [Enter].

Next, select LAN Static Routing and press [Enter]. You must enable static routing by selecting Enabled and pressing [Enter]. After you enable static routing, you must set the route. To do so, select LAN Static Routing Table and press [Enter].
NetWare 5 and NetWare 4.x use different titles for menus, but everything else is the same. For example, NetWare 4.x calls the LAN Static Routing menu choice Static Routing, and it calls the Route Type field on the Static Route Configuration screen Route To Network Or Host. Finally, NetWare 4.x refers to the Next Hop Router on Route field as the Next Hop on Router field. They still do the same things; only the names have been changed
Now, the TCP/IP Static Routes screen will appear. The screen will be empty—don’t panic. We’re going to enter the necessary information. To do so, press [Insert]. You should see the Static Route Configuration screen.

On this window, you’ll tell NetWare where to route your TCP/IP packets. The first field on this window is Route Type. Its default value is set to Network, which won’t work. Press [Enter] to change it. When the Route Type menu appears, select Default Route. The value of the field will change, and you’ll notice that the next two fields become unavailable.

Highlight Next Hop Router on Route. By default, this is set to (Not Specified). To change it, press [Enter] and type the TCP/IP address of the router that you’ve connected to the Internet. If you already have Windows workstations that connect properly to the Internet and don’t know your gateway address, you can find it by running WINIPCFG at any Windows workstation. Enter the value of the Default Gateway field in the Next Hop Router on Route field on your server.

After you’ve made these changes, you must press [Esc] and back out of Inetcfg until you get to the server’s console prompt. Make sure that you save your changes as you go (if it prompts you to). After you get to the server’s console prompt, shut down and restart your server. Rebooting allows the changes to take effect. The Reinitialize Server command should do the same thing, but sometimes we’ve noticed that the changes don’t always apply when you use this command.

When the server restarts, you should test to make sure that you can get out of your network. You can do so by trying to ping your server from a computer connected to an external ISP. You can also try to ping a TCP/IP address on the Internet from your server. To do so, type load ping xxx.xxx.xxx.xxx (placing the IP address in place of the xxx’s) and press [Enter]. The Ping NLM will load and start pinging the address you entered. If everything’s working properly, you’ll see the number of sent and received packets increase in upward increments. Once that works, you’re done! Exit the Ping NLM and go back to work.

Conclusion
When you put TCP/IP on your NetWare server, it won’t route packets to the Internet by default. If you want to run Internet applications on your NetWare server and be able to access it from the Internet using TCP/IP, you must make a few changes in Inetcfg. In this article, we’ve shown you how to configure TCP/IP for the Internet using Inetcfg.

John Sheesley has been supporting networks since 1986, when he got his hands on NetWare 2.2. Since then, he’s worked with the Jefferson County Police Department in Louisville, KY and the Genlyte-Thomas Group. John’s been a technical writer for several leading publishers, including TechRepublic, The Cobb Group, and ZDJournals. If you’d like to contact John, send him an e-mail .

The authors and editors have taken care in preparation of the content contained herein, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for any damages. Always have a verified backup before making any changes.
0 comments