Old SQL Cluster name problems:duplicate name exists on the network

#11

Your discription is a littel unclear as far as which machines were added to
which clusters.

Nevertheless, check Active Directory for any Computer objects for any of the
old cluster virtual network name resources. Check WINS and DNS for address
(A) and/or pointer (PTR) records referring to any of the old cluster network
names.

Good luck.

Sincerely,

Anthony Thomas, MCDBA, MCSA
Senior Consultant
Sogeti USA

"Paul Riker" <PaulRiker (AT) discussions (DOT) microsoft.com> wrote

Quote:

I had a cluster named oldcluster. I created a new cluster called
newcluster.
I evicted node1 from oldcluster, ran "cluster node node1 /forcecleanup. I
changed the dns entry for oldcluster to point to the newcluster ip. Then
added node1 to newcluster.

When I failed newcluster over to node1 I started getting: "you were not
connected because a duplicate name exists on the network"

What would cause "oldcluster" to be broadcast over netbios? How can I
track
this down and burry it for good?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Old SQL Cluster name problems:duplicate name exists on the network

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: Old SQL Cluster name problems:duplicate name exists on the network - 04-27-2008 , 02:25 PM