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 Cards
If you have multiple network cards in a single server, each card must have a different NETwork number, a different PORT address, and a different INTerrupt. You must name each board 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
Adding TCP/IP Protocol
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
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.
"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 , NBI or MSM.NLM.
If Workstations Cannot Attach to the Fileserver
On the server:
- Make sure the volume sys: is mounted.
- Make sure you BIND IPX to the EtherExpress 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, then verify that the EtherExpress adapter in the server and workstation(s) are working and that they are communicating with each other:
- Shut 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 the workstation(s) 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 workstation 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.
NOTE: "Responder not found" is NOT an error. This message will be
displayed IF YOU ARE NOT RUNNING THE SOFTSET/MCADIAGS RESPONDER ON
ANOTHER MACHINE with an EtherExpress card or if the card cannot actually communicate with the responder card. If you do not have a responder running or if the two cards cannot communicate, the diagnostics will try to send packets back to itself.