Trick clients into believing \\Server1 is \\Server2

[JN]

We have a problem where someone hard coded a program to store its data on
\\Server1\MyShare. Well Server1 is being removed for consolidation and will
not be replaced. Renaming \\Server2 is not an option.

I thought I might just stick a second DNS entry in so:

Server1 192.168.1.1
Server2 192.168.1.1

When I ping either Server1 or Server2 I get a response, but when it comes to
linking to network shares or doing a "net view" command I get the following
error:

===========
System error 52 has occurred.

You were not connected because a duplicate name exists on the network.
Go to System in Control Panel to change the computer name and try again\0\0\0===========

Well, my computer name is definetly not duplicated so I think it is just
giving me the wrong description. Is there anything else I can do? The
servers are Windows 2000 SP4

 

[Philip Herlihy]

We have a problem where someone hard coded a program to store its data on
\\Server1\MyShare. Well Server1 is being removed for consolidation and will
not be replaced. Renaming \\Server2 is not an option.

I thought I might just stick a second DNS entry in so:

Server1 192.168.1.1
Server2 192.168.1.1

When I ping either Server1 or Server2 I get a response, but when it comes to
linking to network shares or doing a "net view" command I get the following
error:

===========
System error 52 has occurred.

You were not connected because a duplicate name exists on the network.
Go to System in Control Panel to change the computer name and try again ===========

Well, my computer name is definetly not duplicated so I think it is just
giving me the wrong description. Is there anything else I can do? The
servers are Windows 2000 SP4

This is a guess from someone who isn't an expert, but what the heck...

Consider trying an entry in the client's HOSTS file identifying Server1
with the IP address of Server2. See:

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

http://www.microsoft.com/technet/prodtechnol/windows2000serv/
reskit/cnet/cnbb_tcp_icjk.mspx?mfr=true

An entry in the HOSTS file will be used before DNS is invoked, and you
can have multiple hostnames for one IP address, or use Server2 as an
alias for the Server1 entry (but you'd lose the flexibility of DNS in
the latter case for Server1).

Phil, London

 

[Phillip Windell]

We have a problem where someone hard coded a program to store its data on
\\Server1\MyShare. Well Server1 is being removed for consolidation and
will not be replaced. Renaming \\Server2 is not an option.

I thought I might just stick a second DNS entry in so:

Server1 192.168.1.1
Server2 192.168.1.1

Use a CNAME instead of an A Record

server2 Type=A (HOST) 192.168.1.1
server1 Type=CNAME server2


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Phillip Windell]

You could also give the Server2 the IP# the Server1 had while still keeping
the original IP#. It would be a secondary IP#.

Then create the DNS "A Record" for Server1 with the proper IP#.
You can create a similar entry in WINS.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[JN]

I don't have a problem resolving the name. That works fine in both DNS,
WINS, and even HOSTS files.

The problem is when I actually try to access a shared resource. If I put
Server1's and Server2 's IP address into DNS, WINS and hosts as 192.168.1.1
and ping, tracert, et. I get the correct response back fine not matter what
service is resolving the ip address. But if I create a share "Myshare" and
I try to reach it by \\Server2\Myshare it works fine, but \\Server1\Myshare
gives the error:

===========
System error 52 has occurred.

You were not connected because a duplicate name exists on the network.
Go to System in Control Panel to change the computer name and try again
===========

 

[Phillip Windell]

I don't have a problem resolving the name. That works fine in both DNS,
WINS, and even HOSTS files.

The problem is when I actually try to access a shared resource. If I put
Server1's and Server2 's IP address into DNS, WINS and hosts as
192.168.1.1 and ping, tracert, et. I get the correct response back fine
not matter what service is resolving the ip address. But if I create a
share "Myshare" and I try to reach it by \\Server2\Myshare it works fine,
but \\Server1\Myshare gives the error:

I don't think it is going to do what you want. My description works fine if
it is some other type of service like www or FTP. I do not think it works
with file sharing (which the App appears to depend on). I have multiple
IP#s and Names associated with my File Server due to the Web & FTP Services
that run on it,...but It does not work on it that way with the File Sharing.
With File Sharing I still have to use the real name of the Server.

The only solution I see is to fix the application,...instead of fouling up
the System to satisfy a flawed application. Fix what is really broke,...not
break what isn't.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[david]

Something on your network still thinks that Server1 is still on the network.
If this was just after you turned off Server1, wait 5 minutes and try again.
(Do NOT query while you are waiting). If the problem still exists, you
still have it coded in somewhere.
(Or, ok, you could have a router with a very long cache, but that's less
likely).

If you still have problems, use a network capture/display program like
wireshark to see if the problem is on the client computer, or, if not, which
computer is injecting the false information onto the network.

(david)

I don't have a problem resolving the name. That works fine in both DNS,
WINS, and even HOSTS files.

The problem is when I actually try to access a shared resource. If I put
Server1's and Server2 's IP address into DNS, WINS and hosts as
192.168.1.1 and ping, tracert, et. I get the correct response back fine
not matter what service is resolving the ip address. But if I create a
share "Myshare" and I try to reach it by \\Server2\Myshare it works fine,
but \\Server1\Myshare gives the error:

===========
System error 52 has occurred.

You were not connected because a duplicate name exists on the network.
Go to System in Control Panel to change the computer name and try again
===========

 

[Olof Lagerkvist]

Well, my computer name is definetly not duplicated so I think it is just
giving me the wrong description. Is there anything else I can do? The
servers are Windows 2000 SP4

The problem is that the server checks the target name in the SMB
messages your clients send. You can disable this with a registry setting
and restart the "Server" service.

Read this article: http://support.microsoft.com/kb/281308