DNS Alias Problems with Windows Server 2003 R2

By vabui ·
A colleague of mine discovered today that when he is logged onto the server "Server1" and he tries to connect to a network share using the DNS alias "Alias1", he cannot connect. This is now causing a major problem since we are running macros that have UNC's hard-coded in. Anyone know how to avoid this or have any quick fixes? We could go in and change the UNC for the macros, but just wanted to throw this question out there to see if anyone experienced the same problems. Thanks!

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -


by jareed In reply to DNS Alias Problems with W ...

This is a known issue with 2000 and 2003 servers.

When a client computer connects to a Windows 2000 or 2003 server using an alias, the client receives:
System error 52 has occurred.
A duplicate name exists on the network.
This error occurs when you attempt to connect to the server by using a CNAME alias that is created in the DNS zone:
net view \\alias.<domain>
where alias is a CNAME record that is created for the server in the <domain> zone. Because the server is not listening on the alias, it does not accept connections to that name.

Start ? Run - Regedt32
Create the following DWORD Key manually.

Shutdown and restart the alias should work again.

Collapse -

Don't restart the server

by royce In reply to DisableStrictNameChecking

If you're worryed about the up time of your server (and you should be, it's a *server*), you don't have to reboot the whole system: just resarting the "server" service after making the registary change will work. Don't forget to make sure the "computer browser" service (which depends on the server service) has resarted as well.

Start - Run - Cmd
Net Stop Server
Net Start Server
Net Start "Computer Browser"

Related Discussions

Related Forums