Event success messages 4201 and 1122 using Windows Clustering

View products that this article applies to.

This article was previously published under Q276457

Expand all | Collapse all

SUMMARY

Windows Clustering is dependent upon network communication. The following 1122 and 4201 event success messages are natural occurrences in a clustered environment. These messages occur when one of the nodes is restarted, and then comes back online.

10/2/2000	05:49:47 PM	4	16	1122	ClusSvc	N/A
The node (re)established communication with cluster node Private or 
Public Net Card was reconnected since the other node was rebooted 
and lost communication with the other node.

10/2/2000	05:40:37 PM	4	0	4201	Tcpip	N/A
The system detected that network adapter was connected to the network,
and has initiated normal operation over the network adapter.
The network is now fully functional.

MORE INFORMATION

If this behavior repeatedly occurs and no restart has occurred on the other node, it is an indication that the network is failing which could lead to cluster failure.

When the network is in a functional state, Windows Clustering cannot re-establish communication. An event may be using the Media Sensing feature and never be completely unsuccessful. This behavior may occur if the NIC Teaming feature is wrongly configured on either node.

You can disable the NIC Teaming feature and observe if the problem is resolved. This behavior, however, may also be an indication of a faulty network adapter.

For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

242600 (http://support.microsoft.com/kb/242600/ ) Network failure detection and recovery in a two-node Windows Server 2000 cluster

239924 (http://support.microsoft.com/kb/239924/ ) How to disable Media Sense for TCP/IP in Windows