C
Chris Coates
We have a Windows 2000 AD environment. There is a Win 2K SP4 application
server that we want to use an alias name on, so that the application can be
moved to another server in the future. We will not be changing the name of
the current server when we make that move, therefore the reason for using an
alias.
We added a second IP address to the NIC and created a DNS entry with the
alias name pointing to the second IP address.
Now if we ping the alias the server responds with the new address. If we use
the alias name for Terminal Services or Telnet into the server it works
fine. So clearly name resolution is occurring.
However if we try to map a drive to the alias or do a
\\ServerAliasName\Share we get an error that says "You are not connected
because a duplicate name exists on the network."
We have gotten this to work using a alias DNS name pointing to the same IP
address as the primary one the server has, but we want to use a alias IP
address.
Any suggestions?
Thanks
ccoates
server that we want to use an alias name on, so that the application can be
moved to another server in the future. We will not be changing the name of
the current server when we make that move, therefore the reason for using an
alias.
We added a second IP address to the NIC and created a DNS entry with the
alias name pointing to the second IP address.
Now if we ping the alias the server responds with the new address. If we use
the alias name for Terminal Services or Telnet into the server it works
fine. So clearly name resolution is occurring.
However if we try to map a drive to the alias or do a
\\ServerAliasName\Share we get an error that says "You are not connected
because a duplicate name exists on the network."
We have gotten this to work using a alias DNS name pointing to the same IP
address as the primary one the server has, but we want to use a alias IP
address.
Any suggestions?
Thanks
ccoates