Microsoft KB Archive/247067

From BetaArchive Wiki
Knowledge Base

Article ID: 247067

Article Last Modified on 11/1/2006


  • Microsoft Windows NT Server 4.0 Enterprise Edition, when used with:
    • Microsoft Cluster Server 1.1

This article was previously published under Q247067


When you perform an unattended setup of Cluster Server with multiple network connections declared for client access, Setup may not automatically choose the optimum network connection for the "Cluster IP address" resource. Instead, Setup may use the first network connection that is declared available for client access.


This problem can occur if you have declared more than one network connection as available for client access.


To work around this problem:

  1. Declare only one network connection as available for client access.
  2. Declare all other network connections as "For internal communications only".
  3. After Setup has finished, use the command-line tool Cluster.exe to declare any additional network connections.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.


For additional information about declaring network connections, click the article numbers below to view the articles in the Microsoft Knowledge Base:

174794 How to Change Network Priority in a Cluster

174945 How to Prevent MSCS from Using Specific Networks

Keywords: kbnetwork kbprb kbsetup KB247067