If you have selected one of the Novell® Small Business preconfigured server patterns or installed iManager and WAN Connectivity, you can use the Novell Small Business Setup Role in iManager to help set up Internet Connectivity. Using this tool, you can specify the setup requirements from a browser dialog, and then the setup tool interfaces with inetcfg.nlm to run all the required screens on the server.
This Internet Connectivity task helps you configure the external network interface that goes to the Internet. During the interaction of the utility, you choose whether or not to enable Network Address Translation (NAT). We recommend that you enable this option so that internal packets from the workstations are masqueraded to appear as if they come from the server and packets originating from the Internet to the workstations are rejected unless the connection was first initiated by the workstation. This provides a minimal level of security to your internal network. An exception to this rule is if you are using an external gateway router (or modem) to get to the Internet. If this is the case, you can choose to enable NAT in the gateway and you will not need to enable NAT on the server. Eventually, you will probably want to configure BorderManager® on this server to add packet filtering and proxying capabilities to further protect your internal network.
This Internet Connectivity task collects the information you provide on the Web pages and feeds keystrokes to the server console utility, inetcfg.nlm. You might want to watch the server console as it completes the configuration to see which dialog boxes are being invoked in case you are not familiar with inetcfg.nlm and want to manually make changes on your own later. Also, the configuration might occasionally fail; if it does, you must manually unload inetcfg.nlm, clear the Internet Service Provider Configuration screen, and rerun the utility.
To use the setup task in iManager, open iManager, click Small Business Setup > Set Up Internet Connectivity, and then follow the on-screen prompts.
If you need to modify the settings, you can rerun the setup task or use inetcfg.nlm or the Web-based TCP/IP Configuration utility to make further modifications to your TCP/IP configuration.
The Set Up Internet Connectivity task supports the following connection types:
Telephone Dial-up: NetWare® supports external dial-up modems through the serial port interface. NetWare also supports a variety of internal dial-up modems. However, it doesn't support all modems. For example, it doesn't support WinModems or USB modems.
To see a list of supported modems, select Dial-Up. If your server's internal modem is not on the list, you might need to buy an external modem or a supported internal one.
If you cannot find your modem type in the list, try using "Hayes compatible."
Whichever modem you use, make sure you know the modem type and the settings, including the ISP dial-up number, username, and password. You must also know the name server IP address and default domain name.
DSL (Digital Subscriber Line): If you have a DSL connection to the Internet, it must be an external DSL modem rather than a card that plugs into the server. NetWare doesn't support internal or USB-connected modem hardware. If either of those is what you have, contact your ISP and request an external modem with an Ethernet interface.
IMPORTANT: Also, if your DSL provider requires PPPoE (point-to-point protocol over Ethernet), you must have a gateway modem or router that supports PPPoE because NetWare doesn't support this protocol.
The NetWare server must have an Ethernet board that communicates with the gateway router or the external DSL modem.
You must know the following:
HINT: Normally, you will want to configure your DSL modem in bridge mode so that the server interface is assigned a public IP address. Alternatively, you can use IP address or port forwarding mode so that the server has an external presence.
Cable modem: If you have cable modem, it must be an external cable modem that has an Ethernet interface. NetWare doesn't support internal or USB-connected modem hardware. If either of those is what you have, contact your ISP and request an external modem with an Ethernet interface.
Also, if your cable provider requires PPPoE (point-to-point protocol over Ethernet), you need to have a gateway modem/router that supports PPPoE because NetWare doesn't support this protocol.
You must have an Ethernet board in the NetWare server that communicates with the gateway router or the external cable modem.
You must know the following:
ISDN: The set of supported internal ISDN modems is very small. To see a list of supported modems, select ISDN. If your modem is not on the list, get an external ISDN modem. Even then, only the drivers known at the time of this release are included in this release. Instead, we recommend that you get the drivers from your vendor and follow their instructions for installing them.
You must know the following:
All other configurations: All other configurations must be converted through a modem or gateway router into a standard Ethernet interface.
Install an Ethernet board in the server with an appropriate hub or direct connection to the modem or router. When the server boots, it will try to load and bind to the new hardware. Follow the prompts to get the driver loaded and bound.
You must know the following:
Whichever Internet connection mechanism you use, we recommend that you configure your server with two network interfaces, an external and an internal. These interfaces can consist of two LAN cards, or one dialup/ISDN modem and one LAN card, etc. The external interface is connected or routed to the ISP. The internal interface is typically a LAN interface that is connected to a hub attached to the workstations. The external interface is typically assigned a public IP address (or receives a dynamic address from the ISP), and the internal interface is typically assigned a nonroutable address you provide. For the internal interface, we recommend 192.168.xxx.xxx address numbers. For example, 192.168.1.2 is a good number for the server's internal interface.
In this dual-interface topology, the server acts as a router, firewall, and proxy for the workstations to access the Internet. Packets from the workstations do not go directly to the Internet, but instead must pass through the server. This allows client workstations to use server services such as DNS, DHCP, file sharing, printing, and e-mail without routing to the Internet. This also protects the workstations from security threats that might exist on the Internet.
For more information, see the Novell Netware TCP/ IP Administration Guide for OES in the OES NetWare online documentation.