I have a situation where I have a server named "server1".  I have to
apply changes to 140+ users in the NT domain and I know that I will be
getting a new server in a few weeks so I want to use a new computer
name in DNS called "server5", for now, I need server1 to act as
server5 but windows networking knows server5 is not the actual name of
the computer and gives me an error...

I have read several MS articles on the subject including:
http://support.microsoft.com/defaul...kb;EN-US;222085
How to Scale Microsoft Print Services Using WLBS

http://support.microsoft.com/defaul...kb;EN-US;254210
Cannot Use Net View \\Localhost Command

Which states:

Windows 2000
Error 52
"A duplicate name exists on the network."

CAUSE
This issue can occur because the name localhost is
resolved to the loopback IP Address 127.0.0.1 and
NetBIOS over TCP/IP (NetBT) does not bind to the
loopback address.

In Windows 2000, the SMB device binds to any IP
address (this is why the 'net view' command to the
loopback address works in Windows 2000 and does not
work in Windows NT) but, when the new SMB device
establishes the connection, it checks that it
connected to the right computer by checking the
end point name. This check fails because 'localhost'
is not the name of the local computer.

RESOLUTION
To resolve this issue, use the name of the computer
to see the shares of the local computer. You can use
the Hostname command to obtain the name of the computer.

STATUS
This behavior is by design.


So the point of the article, can I configure server1 so it doesn't
care what name it's being accessed as?

[ Post a follow-up to this message ]

http://support.microsoft.com/?scid=281308
Connecting to SMB Share on a Windows 2000-Based Server May Not Work with an
Alias Name

[ Post a follow-up to this message ]