Filter
Top Products
Problem Probable Cause Corrective Action
• The system has just been
booted and services are still
starting.
• Use the Event Viewer and
look for the following events
logged by the Cluster Service:
Microsoft Cluster
Service
successfully formed
a cluster on this
node.
Or
Microsoft Cluster
Service
successfully joined
the cluster.
• If these events do not appear
in Event Viewer, see the
Microsoft Cluster Service
Administrator’s Guide
for
instructions on setting up the
cluster on your system and
starting the Cluster Service.
The cluster network name is not
responding on the network because
the Internet Connection Firewall is
enabled on one or more nodes.
Configure the Internet Connection
Firewall to allow communications that
are required by MSCS and the
clustered applications or services. For
more information, see the article
KB883398 at support.microsoft.com.
You are prompted to configure one
network instead of two during MSCS
installation.
The TCP/IP configuration is incorrect. The node-to-node network and public
network must be assigned static IP
addresses on different subnets.
The private (point-to-point) network is
disconnected.
Ensure that all systems are powered
on so that the NICs in the private
network are available.
Using Microsoft Windows NT 4.0 to
remotely administer a Windows
Server 2003 cluster generates error
messages.
This is a known issue. Some
resources in Windows Server 2003
are not supported in Windows NT 4.0.
It is strongly recommended that you
use Windows XP Professional or
Windows Server 2003 for remote
administration of a cluster running
Windows Server 2003.
Unable to add a node to the cluster. The new node cannot access the
shared disks. The shared disks are
enumerated by the operating system
differently on the cluster nodes.
Using Windows Disk Administration
ensure that the new cluster node can
enumerate the cluster disks. If the
disks do not appear in Disk
Administration:
1. Check all cable connections.
2. Check the volumes assignments.
3. Select Advanced → Minimum.
44