
UNSOLVED
D
dvhelpdesk
5 Posts
0
2555
March 12th, 2010 05:00
Unistalled Replistor while in alias failover - now get 'duplicate name exists on network' error
I had replistor installed on two servers, with one setup as the alias failover for the other. We don't need to use replication at the moment (need the disk space for other things) so I began unistalling. Unfortunately I was stupid and unistalled from the failover protected server first - so Replistor on the other server kindly took over the alias for what it thought was a failed server. I didn't realise and proceded to unistall Replistor on the failover server. Now I'm getting 'duplicate name exists on network' when I try and use the alias name to access the original server. Somehow Replistor has configured the network to point the alias at the failover server and it didn't go away when I unistalled. How can I reset the network so the alias is available again?
I've tried restarting the two servers involved as well as the domain controller.
I've tried flushing and restarting DNS as well as WINS.
The DNS CNAME entry is correctly pointing to the original server and I can ping the server by the DNS alias no problem, but if I try to us \\alias is get the 'You were not connected because a duplicate name exists on the network' error.
Can anyone tell me how Replistor alias failover really works so that I can reset it and stop this duplicate name?
Responses (0)
Solutions (0)
