If workstations cannot login to the file server:
On the file server:
Verify the NetWare* file server has the frame type Ethernet_802.3 loaded
and that IPX is bound to it.
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 |
NetWare 4.x | 802.2 |
You can verify what frame types you 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 IPX/NETX and run the EtherExpress
adapter 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 IPX/NETX, 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 EtherExpress16 adapter 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 drivers. 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 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.