Troubleshooting Hardware and Network Problems
The following sections provide troubleshooting information for resolving hardware but not really NetWare-related errors.
Identifying Problems after Installation
If the problem occurred after installation, it might indicate that the network was installed incorrectly.
- Check all network boards for conflicting address and I/O settings.
Each component should be able to work as a standalone system.
- Make sure that all cables are fastened securely to all network boards and network connectors, and that terminating resistors are installed correctly.
Resolving Hard Disk Access Problems
To diagnose hard disk access problems, determine whether any of the following conditions exist:
- The disk driver has not been loaded.
- A hard disk is not installed or cabled correctly.
- The communication channel between the controller interface board, the disk coprocessor board, and the hard disk is not functioning.
- The hard disk controller board is not terminated or addressed correctly.
To resolve hard disk access problems, perform the following actions:
- Make sure that the disk driver is loaded. In NetWare Remote Manager, click the Disk / LAN Adapters link in the navigation frame, and then click the Info icon for each network board in your server.
- Check the cables between the hard disks and the controller boards. Make sure that Pin 1 of each cable is attached to Pin 1 of each connector.
- Check the power cables and make sure that they are seated correctly in the power sockets on the hard disks.
- Check the disk partition and volume information on the hard disk using ConsoleOneTM or NetWare Remote Manager.
Making Computer Memory Available for Network Drivers
To increase the amount of workstation memory available for network drivers, do any or all of the following:
- Add more memory.
- Unload unneeded terminate-and-stay-resident (TSR) programs (DOS clients only).
- Modify the NET.CFG file to load only necessary drivers.
- Modify the CONFIG.SYS file to load only necessary drivers.