• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2509
  • Last Modified:

you were not connected because a duplicate name exists on the network

Good morning,

I retired a server from service on our domain over the weekend. there are a number of shortcuts on the network pointing to the old name, so i created a CNAME in DNS pointing to the new server as a work around until I could repair everything.

Computer on the domain come up with the error "you were not connected because a duplicate name exists on the network" I have confirmed that a duplicate name does not exist, and an NSLOOKUP returns the correct information for the cname.

If I attempt to browse to the old server name from a computer that is not on the domain, it connects correctly. We do not have a WINS server, and all of our servers are 2003 or 2008. The PCs are XP or Windows 7.

I have tried the registry entry found in the MS KB, but it has had no effect. any help would be greatly appreciated.
1 Solution
When you retired the old server, did you put in a new/replacement one?

If you put in a new replacement server, was this built from scractch? Or did you use an image from the old one?

Almost sounds like a SID issue and or an AD issue where PCs are trying to re-add themselves to a server which already showing them as already esisting
David Johnson, CD, MVPOwnerCommented:
which computer on the domain is giving the error?
you may have to manually clean out your dns records to remove the remnants of the machine you retired.
you did not state which KB you followed. But this sounds like your issue, and provides a solution


note also the setspn commands at the bottom
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

craigzeiglerAuthor Commented:
The old server was simply removed from the domain. The cname was added to point the old name to a different server.
craigzeiglerAuthor Commented:
That link is what we tried but no luck.

Is the old server an DC controller? Are you cleared the cache (restart the DNS service) after you remove the CNAME?

craigzeiglerAuthor Commented:
The server was not a DC. It was just a terminal server that had a powervault attached. We needed to move the powervault to a more stable server.
craigzeiglerAuthor Commented:
We have dealt with and repaired most of the broken links. I was hoping to find a way to make this a smooth transition, and none of the other answers I have found have worked. There is no reason to keep this open at this point.
craigzeiglerAuthor Commented:
Dealt with the broken links.
Kevin CrossChief Technology OfficerCommented:
Glad you got it figured out. I believe I have seen that in the past and it is an issue with NETBIOS (which is funny as it should be all DNS based now, right :)), but using the CNAME works except from going from command line like Start > Run and \\cname or through shortcuts. It is hard to remember, but I believe having this as an A record where you bind the old server's IP address as an additional IP on the new server or simply changing the old A record to point to the same IP of the new server helped. Just in case this comes up again.

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now