If workstations cannot login to the file server, try these steps:
On the file server:
Verify the Frame type the file server is using is the same as the first
frame type specified in the NET.CFG on your computer. If you do not have
a NET.CFG or do not specify a frame type, EXP16ODI will load 802.2 by
default. Also, Verify that IPX is bound to the loaded frame type at the
server.
Here is a list of the default frame types for NetWare servers:
NetWare 2.x | 802.3 |
NetWare 3.11 | 802.3 |
NetWare 3.12 | 802.2 |
You can verify what frame types your NetWare file server is using by
typing the command "CONFIG" at your NetWare server console screen.
On the workstation:
Reboot the workstation without loading the network drivers and run the
EtherExpress SoftSet/MCADIAGS on-board and on-network diagnostics. If
you have more than one EtherExpress card installed on the network,
reboot the other workstation without loading the network drivers, run
SoftSet/MCADIAGS diagnostics and set this workstation up as a responder.
Rerun the on-network diagnostics on the first workstation and see if
the two machines see each other. This process can be reversed to fully
check communication between the EtherExpress cards. If on-network
diagnostics fail, there is likely a cable, connector, hub or
concentrator problem.
If On-Board diagnostics fail, try setting the EtherExpress 16 to a
different I/O address, a different interrupt, or change Force 8 bit to
"YES".
If On-Network diagnostics fail, there is likely a cable, connector, or
hub problem. Verify that the cabling you are using is connected properly
and that the cable is not defective. For more information on cable
specifications, view the 10BaseT or COAX ethernet cabling readme files
on the EtherExpress LAN adapter and Options disk.
If the on-network diagnostics pass, the boards tested can communicate.
This indicates there could be a problem with the driver usually caused
by loading the wrong frame type on the workstations. Reload the drivers
on the workstation and verify that the 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 diags will try to
send packets back to itself.
Below are sample files for reference:
C:\CONFIG.SYS:
files=25
buffers=25
lastdrive=Z
C:\AUTOEXEC.BAT:
@call c:\nwclient\startnet.bat
path=c:\dos
prompt $P$G
C:\NWCLIENT\STARTNET.BAT:
set nwlanguage=english
c:\nwclient\lsl.com
c:\nwclient\exp16odi.com
c:\nwclient\ipxodi.com
c:\nwclient\vlm.exe
C:\NWCLIENT\NET.CFG:
Link Driver Exp16odi
port 300
frame ethernet_802.2
frame ethernet_802.3
frame ethernet_ii
frame ethernet_snap
NetWare Dos Requester
NOTE: NET.CFG is position sensitive, so be careful to indent lines with
one space or one tab as shown above in the example.