Novell NETWARE 6-DOCUMENTATION Manual page 2904

Monitoring and Resolving Communication Problems
8
(Conditional) If the server doesn't boot automatically from the
AUTOEXEC.BAT file, change to the subdirectory where the
SERVER.EXE file and other boot files are located (the default is
C:\NWSERVER), and enter the following at the DOS prompt:
SERVER
9
(Conditional) If you are using ASPI device drivers (for example, for an
Adaptec* controller), you need to enter one of the following commands:
AHAxxxx
where xxxx specifies the Adaptec board number
or
ASPICD
or
CDNASPI
10
At the console prompt, enter NWPA.
11
(Optional) At the console prompt, enter CD DEVICE LIST.
A list appears with numbers associated with all the devices on your
network. Determine which number is the volume number.
12
At the console prompt, enter
CD9660.NSS
CD MOUNT volume_name|number
13
At the console prompt, enter NWCONFIG.
Problems that occur with networking can originate for any of several reasons:
corrupted hardware or software, bad links, not enough memory, etc.
The following are tips for solving network communication problems.
Check all hubs and repeaters to make sure that they are on.
Check concentrators and look for flashing yellow lights that indicate
collisions.
Make sure that all routers are functioning properly and have enough
memory. A router with insufficient memory becomes the weak link in the
chain and can slow down an entire LAN.
Troubleshooting the NetWare Server 147