There are two drivers provided for the PRO/100 Intel adapter: the ODI Assembly (AHSM) Specification v3.31 driver (E100B.LAN) and the ODI C (CHSM) Specification v1.11 driver (CE100B.LAN). Both are located in the \nwserver directory on the CD. Only CE100B.LAN supports Intel's Advanced Network Services.
NOTE: NetWare 5.x ships with drivers for the PRO/100 Adapters that give base functionality (i.e. connection). To use the Advanced Network Services (such as Teaming and VLAN), use the drivers from the Intel Driver CD.
**IMPORTANT** iANS.LAN is an additional driver used to provide network services such as Teaming and VLAN, which cannot be configured through NWCONFIG.NLM. For instructions on setting up iANS.LAN, see Teaming Tips.
The required minimum versions of the three support NLMs are included on the CD for your convenience.
For NW3.1x
For NW4.1x, 4.2, 5.x
NBI31X.NLM v2.25 10/20/98
NBI.NLM v2.25 9/17/98
MSM31X.NLM v3.95 5/12/99 MSM.NLM v3.95 5/12/99
ETHERTSM.NLM v3.8 3/1/99 ETHERTSM.NLM v3.8 3/1/99
Note: NBI.NLM (or NBI31X.NLM) must be loaded before MSM and ETHERTSM.
NetWare 3.12 needs MSM31X.NLM renamed to MSM.NLM.
Intel recommends you use the latest Novell Service Packs. The latest server NLMs and support files for NetWare can be found on Novell's
automated services under the heading of "Minimum Patch List".
Load Novell's Install.nlm (4.x) or nwconfig.nlm (5.x). For 3.x, see "Instructions for manually loading drivers", below.
From the Installation Options screen, choose "Driver options" and press Enter.
Choose "Configure network drivers" and press Enter. If any drivers are already loaded, a list of them appears.
Choose "Select an additional driver" and press Enter. A list of drivers appears but you will be installing an Unlisted Driver.
Insert the disk and press the Insert key. If the path is not a:\nwserver, press F3 and type in the full path. Press Enter.
CE100b.LAN and E100b.Lan will be displayed. (Only 3.2 and later supports CE100b.LAN.) Choose one and Press Enter. Select Yes to loading the driver. It is up to you if you wish to save the old driver or not.
Next the install utility will give you a choice of Modifying or Saving parameters. If you choose modify, you may move around with the arrow keys. You should specify slot and usually speed and duplex before saving. To avoid parameters (not recommended) you may press the escape key multiple times and back out of the install screens. For more information on parameters, see Command Line Keywords and their Parameters.
The utility will load the driver and assign network numbers for IPX with all four frame types. You may override these numbers by entering your own number at each prompt. (If you wish to limit the number of frame types loaded, edit autoexec.ncf.)
When returned to the Drivers screen, press the Esc key 3 times to exit the utility and return to the prompt.
Copy the PRO/100 server driver and any updated NLMs from \NWSERVER to the NetWare server's hard drive.
If you can't log in to the server (before starting the server) copy
the E100B.LAN driver from the \NWSERVER directory on the Configuration and Drivers disk to the root directory of the server's
hard drive.
If you can log into the server, copy the driver to the SYSTEM
subdirectory. If you do this, you won't need to specify a path on the
load line. If you copy it to another directory, make sure the LOAD
statement includes the correct path.
Start the server. At the server console, load NBI, MSM and ETHERTSM (for NetWare 3.12 load NBI31X, MSM31X and ETHERTSM) in this order. Next, load and bind the server driver.
Add the load and bind statements you need to the server's AUTOEXEC.NCF file so the PRO/100 adapter driver loads automatically each time the server starts.
LOAD E100B SLOT=n SPEED=100 FORCEDUPLEX=2 FRAME=ETHERNET_802.2
BIND IPX TO E100B NET=yy
**IMPORTANT** When using command line options with the .LAN
driver for NWSERVER, make sure the equal sign is followed by a
value. Otherwise, unpredictable results may occur.
See COMMAND LINE KEYWORDS AND PARAMETERS for additional commands and their parameters.
If the error message "Loader cannot find public symbol: <symbol name>" is encountered:
Upgrade the ETHERTSM.NLM and MSM31x, or MSM.NLM and be sure to rename MSM31x.NLM to
MSM.NLM.
Installing multiple adapters:
If you have multiple adapters in a single server, each adapter must
have a different NET number and SLOT number. Also, you may want to
name each adapter. For example:
LOAD C:\E100B SLOT=3 NAME=LAN_A
BIND IPX TO LAN_A NET=222
LOAD C:\E100B SLOT=4 NAME=LAN_B
BIND IPX TO LAN_B NET=333
If you have problems loading the driver on multiple adapters and the
initialization fails due to "Insufficient RCBs," increase the number
of buffers allocated to the server. Add the following to STARTUP.NCF:
SET MINIMUM PACKET RECEIVE BUFFERS = 100 (or larger)
The MINIMUM value you specify should be at least 100 times the number
of PRO/100 adapters in the computer.
The MAXIMUM you can specify depends on the amount of memory in the server, but it must be greater than the MINIMUM. In NetWare 4.1x,
this can be set in the STARTUP.NCF, but NetWare 3.12 requires that
it be set in the AUTOEXEC.NCF:
SET MAXIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)
Installing one adapter with multiple frame types:
When binding multiple frame types to one adapter, enter a LOAD and
BIND statement for each frame type. Each LOAD statement uses the same
SLOT number, but each BIND statement needs a unique network number.
You must also include a name on each load line to avoid being
prompted for the adapter to bind IPX to.
Example:
LOAD C:\E100B SLOT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
BIND IPX TO LAN8022 NET=88888
LOAD C:\E100B SLOT=3 FRAME=ETHERNET_802.3 NAME=LAN8023
BIND IPX TO LAN8023 NET=77777