Microsoft KB Archive/813553

= Connect to Existing Does Not Prompt for Credentials if the Attempt to Connect to the Hosts Does Not Work =

Article ID: 813553

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-





SYMPTOMS
When you use NLBManager either as load host-list or as connect-to-existing, you may not be prompted for new credentials on computers that do not use the default credentials or where the credentials are wrong.



CAUSE
This problem occurs because the thread is processed in the background and it is not designed to provide a user dialog. When you use NLBManager load host-list to connect to a cluster where some of the hosts do not have the same administrator user name and password, NLBManager connects to hosts in a background thread. It uses the default user name and password for all these hosts, and does not prompt for credentials if the attempt to connect to these hosts fails. If the connection fails, NLBManager reports an access-denied message that specifies the hosts that it failed to connect. When you use NLBManager connect-to-existing, NLBManager connects to the first host in the foreground (windows message handling) thread, prompting the user for new credentials if the connection returns access denied. Later hosts in this cluster are connected to in a background thread, and use the credentials of the first host, not the default credentials to connect. As with load-hosts, if any of these later hosts return access-denied, NLBManager fails, and does not prompt for new credentials.



WORKAROUND
To work around this problem, use either method.

Method 1
Individually connect to each host, specifying that host's password. Note NLBManager displays the names of the hosts that it failed to connect to.

Method 2
All hosts in the cluster must have the same administrator user name and password.



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

Keywords: kbprb kbbug KB813553

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.