You may receive error messages if you disable NetBIOS on a Windows Server 2003-based cluster (914056)


The information in this article applies to:

  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

You disable NetBIOS and still use Microsoft Cluster Service (MSCS) on a Windows Server 2003-based cluster. You find that the configuration allows for the IP addresses and network name resources to access each node. However, the configuration does not allow for connections to fully qualified domain names (FQDNs). Additionally, you may experience one or both of the following symptoms:
  • You receive a pop-up error message that is similar to the following:
    \\<FQDN>
    You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
  • You find that a Network Monitor trace captures a "STATUS_DUPLICATE_NAME" error that is consistent with the pop-up error message. However, no error message is logged in the System event log to indicate that a duplicate name exists on the network.

CAUSE

This problem occurs because the Service Location (SRV) service on the server maintains a ServerEndPoint list. However, the NetBIOS name is not in the list. Therefore, the SRV service cannot find the NetBIOS name and sends an error message to the client computer.

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, you must modify the registry, make sure that settings for the public network adapter are correct, and make sure that connections use IP addresses or FQDNs.

Modify the registry

Add the DisableStrictNameChecking registry entry to each node of the cluster if it does not already exist. To do this, follow these steps:
  1. Start Registry Editor.
  2. Locate the following registry key:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanserver\parameters

  3. On the Edit menu, click Add Value, and then add the following:
    Value nameData typeValue
    DisableStrictNameCheckingREG_DWORD1
  4. Exit Registry Editor and restart the computer.

Examine the settings for the public network adapter

  • Make sure that you click to select the Register this connection's addresses in DNS check box for the public network adapter.
  • Make sure that the DNS server addresses appear on the Internet Protocol (TCP/IP) Properties page for the public network adapter. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

    825036 Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

Examine the connections for IP addresses or FQDNs

Make sure that the public network adapter connections use IP addresses or FQDNs.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, visit the following Microsoft TechNet Web site:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/clstntbp.mspx

Modification Type:MajorLast Reviewed:3/31/2006
Keywords:kbtshoot kbprb KB914056 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.