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
However, the configuration does not allow for connections to fully qualified
domain names (FQDNs). Additionally, you may experience one or both of the
- You receive a pop-up error message that is similar to the
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.
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.
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
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:
- Start Registry Editor.
- Locate the following registry key:
- On the Edit menu, click Add
Value, and then add the following:
Collapse this tableExpand this table
|Value name||Data type||Value|
- 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
- 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:
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.
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
For more information, visit the following Microsoft TechNet