Chapter 2: Configuring TCP/IP

Previous Page Next Page

2.2.2.1 Using INETCFG

If you are running NetWare 4.11, IntranetWare, Novell’s Multi-Protocol Router, NetWare for SAA or other advanced communication service, you can use the NetWare INETCF.NLM utility to examine your existing LAN driver setup. To load INETCFG, type the following command at the NetWare console prompt:

:LOAD INETCFG <Enter>

If you receive error messages such as "Failed to find load file INETCFG" then you do not have INETCFG installed. You should skip to section 2.2.2.2 Using EDIT to Read AUTOEXEC.NCF or section 2.2.2.3 Using CONFIG to determine the LAN driver information.

If INETCFG loads but you are prompted to import settings from the AUTOEXEC.NCF file, then INETCFG has not yet been configured as the primary management point for the LAN drivers and protocols. You may choose to allow INETCFG to automatically import the LAN driver and protocol settings, although you will need to refer to the NetWare documentation for instructions on how to do this. If you do not wish to do this at this time, then skip to section 2.2.2.2 Using EDIT to Read AUTOEXEC.NCF or section 2.2.2.3 Using CONFIG to determine the LAN driver information.

If INETCFG loads successfully, you will be presented with a console screen similar to the following:

Undisplayed Graphic

Figure 2.3: INETCFG main screen.

Select the "Boards" menu option and press <Enter>. You will be presented with a screen similar to the following:

Undisplayed Graphic

Figure 2.4: INETCFG's "Configured Boards" settings.

If your network adapter does not show up in this screen, then you are not using INETCFG to manage your LAN drivers and protocols (although you may be using it to manage your WAN drivers and protocols). You should skip to section 2.2.2.2 Using EDIT to Read AUTOEXEC.NCF or section 2.2.2.3 Using CONFIG to determine the LAN driver information.

Use the information provided in this screen to fill out the "LAN Driver Information" portion of the form in Figure 2.1.

  1. Note the information provided under the "Driver" heading, and write it down in the "LAN Driver Filename" field of the configuration worksheet. In the example shown above, the "LAN Driver Filename" field would contain "SMC8000".

  2. Note the information provided under the "Int," IOAddr," "MemAddr" and "Slot" headings, and write it down in the "LAN Driver LOAD Parameters" field of the configuration worksheet. In the example shown above, the "LAN Driver LOAD Parameters" field would contain "INT=A PORT=240 MEM=CC000".

Press <Esc> to close the "Configured Boards" window, and then select the "Network Interfaces" menu item and press <Enter>. You will be presented with a screen similar to the following:

Undisplayed Graphic

Figure 2.5: INETCFG’s "Network Interfaces" settings.

Use the information provided in this screen to fill out the "LAN Driver Information" portion of the form in Figure 2.1.

  1. Note the information provided under the "Media" heading, and write it down in the "LAN Topology/Medium" field of the configuration worksheet. Check the appropriate box in the "LAN Topology/Medium" field of the configuration worksheet. In the example shown above, the "LAN Topology/Medium" field would have a check next to "Ethernet".

  2. Determine whether the "Frame Type for TCP/IP" field in the configuration worksheet should be "ETHERNET_II" or "TOKEN-RING_SNAP". The "TOKEN-RING_SNAP" option is used for both Token Ring and FDDI adapters. Check the appropriate box in the "Frame Type for TCP/IP" field of the configuration worksheet. In the example shown above, the "Frame Type for TCP/IP" field would have a check next to "ETHERNET_II".

  3. You can ignore the configuration worksheet’s "Name to Assign this Frame Type" field, as INETCFG will automatically assign one for you when you reload the LAN driver.

Press <Esc> to close the "Network Interfaces" window, and then press <Esc> again to close INETCFG and return to the NetWare console prompt.

STEP: To continue to the next step in the configuration process, go to section 2.2.3 Determine the IP Protocol Information.

Previous Page Next Page

Copyright 1997 Unoverica Corporation, All Rights Reserved page
Send comments to docs@unoverica.com