This document applies to the EtherExpress 16, 16TP, 16C, FLASH,
FLASH TP, FLASHC, MCA, and MCA/TP adapters. It contains notes for
installing the Novell NetWare* 3.1x server driver and troubleshooting
tips. To configure an EtherExpress adapter, see the printed
installation guide.
The current version of the EtherExpress 16 LAN Adapter Configuration and
Driver disk, file E16DISK.EXE is available through Intel's online
services.
Before You Start
You must configure and test the EtherExpress 16 adapter with
SOFTSET.EXE. Boot the workstation with DOS, then insert the EtherExpress
16 LAN Adapter Configuration and Driver disk into drive A. At the DOS
prompt type:
A:SOFTSET
- Choose "AUTOMATIC SETUP" to let SOFTSET configure the EtherExpress
adapter to work in your computer, or select "MANUAL SETUP" if you want
to designate which interrupt and I/O address you want the EtherExpress16
to use.
- Choose "RUN DIAGNOSTICS" from the main menu to test the configuration
you
have selected.
Required Nlms For NetWare 3.1X
For 3.12 Servers
This version of EXP16.LAN auto-loads two Novell NLMs (ETHERTSM and
MSM31X) when you load the EXP16.LAN driver. You may need to update the
versions of these two NLMS currently installed on your NetWare 3.12 file
server to version 2.31 or later:
MSM31X.NLM (06-28-94 v2.31)
ETHERTSM.NLM (06-28-94 v2.31)
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 EtherExpress16 driver disk in the
directory \NWSERVER\NLM in a self-extracting file called NLMS.EXE. Copy
the file NLMS.EXE onto the C: drive of your file server and then run it
to extract the files.
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, make sure the LOAD
statement includes the correct path.
For 3.11 Servers
This version of EXP16.LAN auto-loads four Novell NLMs (ETHERTSM, MSM31X,
LSLENH and PATCHMAN) when you load the EXP16.LAN driver. You may need to
update the versions of these four NLMS currently installed on your
NetWare 3.11 file server to these versions:
PATCHMAN.NLM | (10-05-93 v2.30) |
LSLENH.NLM | (10-05-93 v1.01) |
MSM31X.NLM | (06-28-94 v2.31) |
ETHERTSM.NLM | (06-28-94 v2.31) |
MONITOR.NLM | (10-26-92 v1.75) |
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 16 driver disk in the
directory \NWSERVER\NLM in a self-extracting file called NLMS.EXE. Copy
the file NLMS.EXE onto the C: drive of your file server and then run it
to extract the files.
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, make sure the LOAD
tatement includes the correct path.
NOTE: MONITOR.NLM is not auto-loaded by EXP16.LAN but should be updated
to v1.75 version or later.
General Installation
- From the DOS prompt on the server, copy the EtherExpress adapter
driver (\NWSERVER\EXP16.LAN) to the Novell NetWare directory on the DOS
partition of the server's hard drive (drive C:).
- From the DOS prompt on the server, copy the updated Novell NetWare
NLMs to the Novell NetWare directory on the DOS partition of the
server's hard drive (drive C:).
- Start NetWare by typing SERVER or the name of your startup batch
file.
- Load the updated Novell NetWare NLMs.
For NetWare 3.11, type:
LOAD C:<PATH>\PATCHMAN
LOAD C:<PATH>\LSLENH
LOAD C:<PATH>\MSM31X
LOAD C:<PATH>\ETHERTSM
For NetWare 3.12, type:
LOAD C:<PATH>\MSM31X
LOAD C:<PATH>\ETHERTSM
- Load the driver. At the server's colon (:) prompt, type:
- LOAD C:<PATH>\EXP16 PORT=xxx INT=y
WHERE: xxx is the I/O address of the EtherExpress card and y is the
interrupt (IRQ) in hexadecimal numbers.
SoftSet and the System Configuration utility display the IRQ in decimal.
IRQ10 = A in Hex. IRQ11 = B in Hex.
Be sure to include the path to the driver's location.
Novell provides several other parameters you can include in the LOAD
statement, but they are not required. For more information on those
parameters and when you should use them, see the NetWare Installation
manual.
- Bind the driver. At the server's colon (:) prompt, type:
- BIND IPX TO EXP16 NET=xx
WHERE: xx is the external network number.
At this point you should be able to log into the server from a
workstation.
To Make This Permanent
Using Novell's INSTALL program, edit the AUTOEXEC.NCF file to add the
LOAD and BIND statements for the EtherExpress 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 no parameters. From
the Colon prompt, type:
LOAD C:<PATH>EXP16
NetWare will prompt you for the interrupt and port address. 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 EXP16
Installing Multiple Etherexpress Adapters
If you have multiple network adapters in a single server, each adapter
must have a different NETwork number, a different PORT address, and a
different INTerrupt. You must name each adapter using the "NAME="
parameter. For example:
LOAD C:\EXP16 PORT=300 INT=3 NAME=LANA
BIND IPX TO LANA NET=10
LOAD C:\EXP16 PORT=350 INT=5 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 PORT address
and INTerrupt, but a different NETwork number. You must name each board
using the "NAME=" parameter. For example:
LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
BIND IPX TO LAN8022 NET=10
LOAD C:\EXP16 PORT=300 INT=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 adapter to TCPIP. For example:
LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_802.2 NAME=LAN_IPX
BIND IPX TO LAN_IPX NET=1
LOAD C:\EXP16 PORT=300 INT=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 the
NetWare 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 MSM31X.NLM. Verify that you are loading version 2.31 or
later of these NLMs.
If Workstations Cannot Attach To The File Server
On the server:
- Make sure the volume SYS: is mounted.
- Make sure you have a BIND IPX line for the EtherExpress driver.
- Make sure the FRAME type is the same on server and workstation. The
default frame type is 802.2 (NetWare 3.12) or 802.3 (NetWare 3.11).
If both of these have been checked and workstations still cannot attach
to the file server, then verify that the EtherExpress adapters in the
server and workstations are working and that they are communicating with
each other:
- Down the file server and reboot with DOS. Run the SOFTSET/MCADIAGS
on-board and on-network diagnostics. If these pass, set the file server
up as a responder in SOFTSET/MCADIAGS diagnostics.
- Reboot each workstation without loading IPX/NETX and run the
SOFTSET/MCADIAGS on-board and on-network diagnostics. During the
on-network diagnostics, the server (set up as a responder) should count
and echo the packets sent by the workstation.
- Rerun the workstation and set it up as a responder and try the
on-network diagnostics from the server machine.
- If on-network diagnostics fail, there is likely a cable, connector,
hub or concentrator problem.
If the on-network diagnostics pass, the boards tested can communicate.
This indicates there could be a problem with the drivers. Bring the
server machine back up as a server. Reload the drivers in the
workstation. If the workstation still cannot connect to the server,
there is likely a problem with the configuration of the drivers. Verify
that the server and worrkstation drivers load properly. You can do this
by loading them one at a time, rather than in a batch file, and watch
for error messages.
PLEASE NOTE:
This product is no longer being manufactured by Intel. THESE DOCUMENTS ARE PROVIDED FOR HISTORICAL
REFERENCE PURPOSES ONLY AND ARE SUBJECT TO THE TERMS SET FORTH IN THE "LEGAL" INFORMATION" LINK BELOW.
For information on currently available Intel products, please see
www.intel.com and/or developer.intel.com
|