Fix: 0x80070034 You were not connected because a duplicate name exists on the network.
Every company with branch offices should consider the use of DFS (replicated or not) to maintain a consistent shares structure and data availability across all locations. With DFS Namespaces technology, you can group shared folders located on different servers by transparently connecting them to one or more namespaces. That namespaces are hosted on namespace servers, usually member servers or domain controllers.
Today I’ve searched around trying to get some guidance with Event ID 4098 combined with error code 0x80070034 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.
Let me describe the conditions of the environment in which we are moving:
- You are trying to map a network drive to a DFS namespace path.
- The namespace server has been renamed.
- A CNAME with the old server name has been kept on the DNS servers.
When you try to connect to the server by using a CNAME alias that is created in the DNS zone it is not “listening” on the alias, and therefore is not accepting connections to that name.
To resolve this problem in Windows Server 2003, follow these steps:
- Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
- Apply the following registry change to the file server. To do so, follow these steps:
-
Start Registry Editor (Regedt32.exe).
-
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
-
On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1 -
Quit Registry Editor.
-
- Restart your computer.
You may also have to set the SPN (Service Principal Name) for the Alias Name.
-
**_setspn -a host/aliasname.domain.com targetserver_**
Extend this information on the link below: