A file server by any other name: Errors when using a DNS Alias in a UNC Path.

Computers are mean. Here’s a robot.

You’re using a DNS Alias to access an SMB network share on a Windows 2003 server, and you get the following error:

“System error 52 has occurred.
A duplicate name exists on the network.”

This is a known issue with Windows 2000 and Windows 2003 based servers. If a DNS alias is created for a server, the server doesn’t know to listen for connections from computers that are trying to access it’s file shares. This issue has been fixed in later versions of Windows but if you’re dealing with say a Windows 2003 server, you’re going to have to make a change to the registry of the server that the alias was created for and then reboot it. You may also have to set the SPN (Service Principal Name) of the server to match the alias.

 

Further info and instructions can be found in the link below.

http://support.microsoft.com/kb/281308

Advertisements