Problems With Windows Server 2003 - NEC SA2500 User Manual

User Guide
■ Are the optional SCSI controllers properly configured?
- When the system has an optional SCSI controller installed and SCSI devices
connected to it, use the POST Setup utility that comes with the optional SCSI
controller for proper configuration. See the manual that comes with the optional
SCSI controller for details.
The system is not found on the network:
■
Is the LAN cable connected?
- Make sure to connect the LAN cable to the network port on the rear of the sys-
tem. Also make sure that the LAN cable to use conforms with the network
interface standard.
■ Is the BIOS configuration correct?
- The internal LAN controller may be disabled with the BIOS SETUP utility of
the system. Check the setting with the BIOS SETUP utility.
■ Ηave the protocol and service already configured?
- Ιnstall the distinctive network driver for the system. Make sure that the proto-
col, such as TCP/IP, and services are properly specified.
■ Ιs the transfer speed correct?
- Open the network property dialog box in control panel to specify the "Link
Speed & Duplex" value the same as the value specified for HUB.
Wake on LAN does not start from standby state.
■ Ιs Hub set to Auto-Negotiation? Or, Is the client set to Auto-Negotiation/optimum
speed?
- For both hub and client, Wake on LAN does not start from the standby state if
the speed is fixed to 1000Mbps.

Problems with Windows Server 2003

A log appears and no network cable is connected to the network port:
When network cable is not connected with a port, a log (see the example below) may
be found in event log. But this has no affect on the behavior of Lan driver.
Event ID: 6
Source: E100B
Type: Error
Description: Hardware failure detected.
Machine: (Name of your system)
Lan: 100BASE
Solution: Connect a network cable in a port and then reboot the system or change the
[Smart Power Down] value to "Off", the log will not be found in event log any more.
197
www.nec-computers.com