You hit ERROR_DUP_NAME (0X00000034) — the duplicate computer name problem
It's annoying when Windows just refuses to connect and throws this error. But the root cause is simple: your computer name matches another device on the same local network. NetBIOS (used by older Windows networking and SMB) can't have two machines with the same name — it breaks name resolution completely.
The quick fix: Rename your computer
- Open Settings > System > About (Windows 10/11).
- Click Rename this PC.
- Pick a name that's unique on your LAN — avoid generic names like "DESKTOP-ABC123" or names matching other devices you see in your router's client list.
- Restart the computer when prompted.
That's it for 90% of cases. After the restart, try connecting to the network share again. The duplicate name is gone.
Why does renaming fix it?
What's actually happening here is that Windows broadcasts its NetBIOS name over the network during startup. If another device responds with the same name, the network stack marks your machine as a duplicate and refuses to participate in browsing or file sharing. The error code 0X00000034 is the kernel telling the SMB redirector: "I can't connect because this name is already claimed." Renaming your PC gives you a new, unique identifier — the conflict disappears. The reason renaming works instead of just disabling NetBIOS is that many enterprise networks still rely on NetBIOS name resolution for legacy compatibility. Turning it off can break other things like network discovery or printer sharing.
When renaming alone doesn't work
Sometimes the duplicate isn't your computer — it's another machine that was cloned, has a static NetBIOS name, or was set up with the same hostname. Here are the less common variations of this issue:
1. Virtual machine clones
If you're running Hyper-V, VMware, or VirtualBox and cloned a VM without running sysprep, the clone inherits the same computer name. This is the most common cause in lab environments. The fix: rename the cloned VM, or better, run sysprep /generalize /oobe before cloning next time.
2. Static IP with duplicate hostname in DNS
If your network uses static IPs and the hostname in DNS points to two different IPs, NetBIOS can still detect the conflict. Check your DNS records — remove the old A record for the duplicate name.
3. Disabled NetBIOS over TCP/IP
This sounds backwards, but some networks disable NetBIOS but leave NetBIOS name resolution enabled on clients. If one machine has NetBIOS disabled and another doesn't, the conflict can still appear because the broadcast packets still collide. Go to Network Connections > right-click your adapter > Properties > Internet Protocol Version 4 (TCP/IPv4) > Advanced > WINS tab. Set NetBIOS setting to Default or Enable NetBIOS over TCP/IP on both machines for consistency.
4. Workgroup vs Domain conflict
If you're on a domain, a computer with the same name in a workgroup can still cause this error. The domain controller broadcasts the name, and the workgroup machine responds — boom, conflict. Solution: rename the workgroup machine or join it to the domain if that's appropriate.
Prevention: Avoid duplicate names before they happen
Three things to do now so you don't see 0X00000034 again:
- Document your hostnames. Keep a simple spreadsheet of every computer on your LAN with its name, IP, and MAC. When you add a new machine, check the list first.
- Use DHCP reservations. Assign static IPs for critical machines via your router's DHCP reservation list — this prevents IP conflicts that sometimes trigger duplicate name errors indirectly.
- Always sysprep cloned VMs. If you copy a virtual machine disk image, run sysprep before the first boot. It regenerates the SID and computer name, guaranteeing uniqueness.
If you're still stuck after renaming and checking the above, the problem is likely deeper — maybe a third-party firewall blocking NetBIOS broadcasts, or a misconfigured WINS server. But for 99% of readers, renaming your PC and restarting is the end of the story.