User Guide

Troubleshooting the NetWare Server 155
Server Operating System Administration Guide
103-000148-001
August 30, 2001
Novell Confidential
Manual 99a38 July 17, 2001
click the Disk / LAN Adapters link in the navigation frame, and then click
the name link for each of the network boards in your server.
For tips on troubleshooting communications problems, see “Tips for
Resolving General Communication Problems” on page 156
If necessary, use LANalyzer
®
or a similar product to monitor network
traffic and isolate the problem.
6 Make sure server utilization is normal.
Check utilization statistics. For help in responding to high utilization, see
“High Utilization Statistics” on page 125.
If you suspect heavy LAN traffic is causing the problem, try unplugging
the LAN cable. If heavy LAN traffic was the problem, utilization should
drop.
7 Make sure the server has sufficient resources.
Is the server receiving No ECB Available Count messages or messages
about insufficient packet receive buffers?
These messages could indicate that the server is running out of resources.
For help in resolving these errors, see “Insufficient Packet Receive
Buffers, No ECB Available Count Errors” on page 121.
8 Make sure the eDirectory database is functioning.
Is the eDirectory database closed or locked by another utility, such as
DSREPAIR?
If the eDirectory database is not functioning, the workstation clients will
not display the login screen.
9 Check for -625 or other communication errors at the server.
Are servers receiving -625 or other communication errors?
If so, see “Unable to Communicate with Server, -625 Errors” on page 150
or see the online documentation Novell Error Codes (http://
www.novell.com/documentation/lg/nwec/docui/index.html) > NDS or
eDirectory Error Codes.
If the problem still occurs, follow the troubleshooting steps in “Using a
Troubleshooting Methodology” on page 105, search the Novell
Knowledgebase (http://support.novell.com/search/kb_index.jsp), and contact
a Novell Support Provider.