- 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.
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 registryAdd 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: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanserver\parameters
- On the Edit menu, click Add Value, and then add the following:
Value name Data type Value DisableStrictNameChecking REG_DWORD 1
- 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 FQDNsMake sure that the public network adapter connections use IP addresses or FQDNs.
Article ID: 914056 - Last Review: Mar 29, 2017 - Revision: 4