Loss of Connection with Node Persists Until Node Is Restarted

Article translations Article translations
Article ID: 238009 - View products that this article applies to.
This article was previously published under Q238009
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

Symptoms

When you use Microsoft Cluster Server (MSCS) and one node loses its connection with another node, subsequent attempts to re-establish the connection may not be successful until the second node is restarted. Note that the second node can be either a cluster node or a sponsor node.

This behavior may also occur when you install a cluster node to join a sponsor node and you cannot establish the connection on the first attempt. When the initial join does not complete, all subsequent attempts to join the sponsor node are also unsuccessful until you restart the sponsor mode.

Resolution

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
  • Windows Service Pack Center -or-

  • 152734how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/contactus/?ws=support

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Status

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

More information

The primary issue of this behavior is the join (connection) on the second node. Although the occurrence of this behavior is rare, it can occur potentially every time a connection between nodes is unsuccessful or stops, and an attempt is made to re-establish the connection.

The operating system on the first node is not critical in this situation, you can use any operating system that supports Windows NT Server, Enterprise Edition. However, you must apply Windows NT 4.0 Service Pack 6 or later on the operating system of the second node.

Properties

Article ID: 238009 - Last Review: November 2, 2013 - Revision: 3.0
Applies to
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbinterop kbnetwork KB238009

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com