NCR WorldMark 4300, Product Manual, Page: 73 / 100

Diagnostics
WorldMark 4300 Server Management Product Manual B-7
Services Troubleshooting Procedure
•
Same as above
Server Shut Down for Unknown Reason
Possible Causes
•
Critical hardware status
•
Someone else shut down the server
User Troubleshooting Procedure
•
Review diagnostic partition logs
•
If the server is now up, review the Chassis Event Log or the Single Byte Event Log via out-
of-band
Services Troubleshooting Procedure
•
Same as above
Could Not Auto-discover Server Under LANDesk
Possible Causes
•
Use of inappropriate LANDesk console transport to discover server type
•
Server is not up or is not running LANDesk
•
UNIX network not configured
•
UNIX server is configured for multi-cast versus broadcast
User Troubleshooting Procedure
•
Verify correct LANDesk console transport icon is selected while executing Configure >
Rebuild Server List. Select Microsoft Windows Network icon to discover Windows NT
servers and select UNIX Hosts icon to discover UNIX servers.
•
For UNIX servers, verify the network in which your server exists has been configured. Select
UNIX Hosts icon then view your network in the Configure > Communications > Networks
dialog. If needed, add the network in which the server exists by specifying a network name,
the network IP address, and the network mask. Retry the UNIX Hosts auto-discovery.
•
Use network ping command to the server IP address to verify server and network services are
running.
•
Use telnet to login to the server to verify it is running LANDesk server component. For
Windows NT server, verify the Intel Server Monitor Service is running and start the service,
if needed, via the Control Panel Services applet. For UNIX server, verify the LANDesk