Networking

Duplicate Name Exists on the Network when using DNS Alias

When a client computer connects to a Microsoft Windows 2000-based computer or a Microsoft Windows Server 2003-based computer by using an alias name, the client may receive the following error message:

A duplicate name exists on the network.

Although, you're able to access the computer by FQDN or IP address, you're unable to access it by using DNS alias.

This problem can occur when you try to connect to the server by using a CNAME alias that is created in the DNS zone. For example, this problem may occur with a command similar to the following sample command

net view \\alias.domain name.com

where alias is a CNAME record that is created for the server in the domain name.com zone. The server is not "listening" on the alias, and therefore is not accepting connections to that name.

Here's how to fix this on Windows Server 2003 

To resolve this problem in Windows Server 2003, follow these steps:

  1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
  2. Apply the following registry change to the file server. To do so, follow these steps:
    1. Start Registry Editor (Regedt32.exe).
    2. Locate and click the following key in the registry:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
    3. 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
    4. Quit Registry Editor.
  3. Restart your computer.

You may also have to set the SPN (Service Principal Name) for the Alias Name.
For example, you may have to enter a command that resembles the following commands:

setspn -a host/aliasname targetserver
setspn -a host/aliasname.contoso.com targetserver

PrintEmail

Comments   

 
MarvinB
0 #12 MarvinB 2013-03-12 13:10
Wow, Thanks for this resolution.The other options I found were a lot more complicated. Thanks to Chris also for the note about the server service.
Quote
 
 
Ajay
0 #11 Ajay 2013-01-14 11:54
This worked for me. Thanks a lot. :lol:
Quote
 
 
M@H
-1 #10 M@H 2012-11-18 07:52
Thank You ..... Its worked .
Quote
 
 
mark myers
+1 #9 mark myers 2012-11-06 16:04
thanks for this artical. it worked perfect
Quote
 
 
Jon Carr
+3 #8 Jon Carr 2012-10-25 10:31
Thanks for this tip, the regedit fix resolved my issue on a WINDOWS 2008 R2 server too.
Quote
 
 
Hary
+1 #7 Hary 2012-10-02 14:25
This is great solution and explanation. Thanks!
Quote
 
 
Abhishek Dalmia
+1 #6 Abhishek Dalmia 2011-12-01 17:02
Worked ......thanks
Quote
 
 
John
-1 #5 John 2011-10-07 17:16
You just made my day with this!!!!!!!!!!! !!!
Quote
 
 
mrcrassic
+1 #4 mrcrassic 2010-11-06 06:11
this worked! thanks!
Quote
 
 
Prasad
-1 #3 Prasad 2010-07-23 05:49
This worked for me too. Thanks for sharing.
Quote
 

Add comment


Security code
Refresh