This document applies to the EtherExpress 32N LAN adapters.
General Installation
- Install NetWare 4.1x according to the NetWare* 4.1x installation
manual.
- When prompted to select the server network driver, select Intel
EtherExpress 32 adapter.
- Configure the LAN driver by entering the EISA SLOT Value. Press F10
to exit the setup program and load the driver.
- Continue with the NetWare 4.1x installation.
NOTE: 4.01 or 4.02 Servers
This version of NE3200.LAN auto-loads two Novell NetWare NLMs (ETHERTSM
and MSM) when you load the NE3200.LAN driver. You may need to update the
versions of these two NLMS currently installed on your NetWare 4.01 or
4.02 file server to these versions:
MSM.NLM | (11-23-94 v2.50) |
ETHERTSM.NLM | (11-29-94 v2.50) |
Make sure you use these (or later) versions. Earlier versions may not
work properly or generate this error message:
"Loader cannot find public symbol: <symbol name>"
These updated NLMs are located on the EtherExpress 32 adapter driver
disk in the directory \NWSERVER\NW4X.
If you can log in to the server, copy these updated NLMs into 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 on the local drive, make
sure the LOAD statement includes the correct path.
For NetWare 4.01 and 4.02, add these lines to the AUTOEXEC.NCF before
loading NE3200.LAN:
LOAD C:<PATH>\MSM
LOAD C:<PATH>\ETHERTSM
LOAD C:<PATH>\NE3200 SLOT=X
where X is the slot value of the EtherExpress 32 LAN adapter.
Troubleshooting Tips
TROUBLE LOADING THE DRIVER
If you have problems loading a driver, remove the driver statements from
the AUTOEXEC.NCF file and enter them manually with noparameters. From
the Colon prompt, type
LOAD NE3200
NetWare will prompt you for the SLOT value. Add parameters back one at a
time. If you receive any error messages, check the NetWare System
Messages manual for an explanation.
Do the same for the BIND statement. Type
BIND IPX TO NE3200
Installing Multiple EtherExpress Cards
If you have multiple network cards in a single server, each card must
have a different network number and different SLOT value. You must name
each board using the "NAME=" parameter. For example,
LOAD NE3200 SLOT=3 NAME=LANA
BIND IPX TO LANA NET=10
LOAD NE3200 SLOT=4 NAME=LANB
BIND IPX TO LANB NET=20
Do not confuse the NETwork number with the internal IPX number; they
need to be different. See the NetWare Installation manual for more
information.
Installing One EtherExpress Card With Multiple Frame Types
When binding multiple frame types to one card, enter a LOAD statement
for each frame type. Each LOAD statement will use the same SLOT value,
but a different network number. You must name each board using the
"NAME=" parameter. For example,
LOAD NE3200 SLOT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
BIND IPX TO LAN8022 NET=10
LOAD NE3200 SLOT=3 FRAME=ETHERNET_II NAME=LANII
BIND IPX TO LANII NET=20
Do not confuse the network number with the internal IPX number; they need
to be different. See the NetWare Installation manual for more
information.
TCP/IP
If you are using NetWare's TCP/IP NLM, you must load an ethernet type II
frame and bind the EtherExpress to TCPIP. For example,
LOAD NE3200 SLOT=3 FRAME=ETHERNET_802.2 NAME=LAN_IPX
BIND IPX TO LAN_IPX NET=1
LOAD NE3200 SLOT=3 FRAME=ETHERNET_II NAME=LAN_IP
LOAD TCPIP
BIND IP TO LAN_IP ADDR=xxx.xxx.xxx.xxx
WHERE: xxx.xxx.xxx.xxx is your internet address.
You may also have MASK and GATE parameters on the BIND IP line. See
NetWare's documentation for more information.
ERROR MESSAGE: "Loader cannot find public symbol: <symbol name>" "Load
file referenced undefined public variable"
This error message occurs when the server is loading older versions of
ETHERTSM.NLM or MSM.NLM. Verify that you are loading version 2.50 or
later of these NLMs.
If Workstations Cannot Attach to the Fileserver
- Make sure the volume sys: is mounted.
- Make sure you BIND IPX to the EtherExpress adapter driver.
- Make sure the FRAME type is the same on server and workstation. The
default frame type is 802.2
If both of these have been checked and workstations still cannot attach
to the file server, verify that the EtherExpress adapters in the server
and workstation(s) are working and that they are communicating with each
other.
* Third-party trademarks are the property of their respective owners.