Clean DNS, DHCP, and Active Directory of Old Server Names

I am trying to create a cluster. The company has a specific server naming scheme and specific IP addresses I need to assign to each server. Here is the problem I have. I restore two servers and I have nothing but a clean workgroup install. I joined the two servers to the domain. Default names are xx1 and xx2. I need them to say Node03 and Node04.

I ran cluster validation wizard while the servers were named x1 and xx2 with DHCP assigned IP addresses. Everything works perfect. I change the names to Node03 and Node04 and assign a static IP to each server and suddenly I cannot connect the servers for cluster validation.

I get failed to connect to service manager from one of the nodes. When i run it from the other node I am able to validate but get this error.

DHCP status for network interface Node03.domain.com - MY LAN differs from network Cluster Network 1.

I think the problem is that there were earlier versions of Node03 and Node04 on the domain. Now when i rename the computer back to those names and give them the same IP address I cannot connect.

These were not domain controllers. How can I completely clean the local computer of old names because I must have renamed these two machine 4-5 times already.

How can I clean active directory, dns, dhcp, from all reminants of these two nodes so it looks like I'm joining node 3 and node 4 for the first time to the network with their IP addresses also fro the first time.

These are 2008 server R2 systems on a 2008 server R2 domain.
MEATBALLHEROAsked:
Who is Participating?
 
warddhoogheConnect With a Mentor Commented:
while the server has the correct name and static IP,
open a cmd and run: ipconfig /registerdns

that will register the name over any existing previous record in dns, and probably solve your problem. if not, then after the action execute ipconfig /flushdns on all machines involved
0
 
MEATBALLHEROAuthor Commented:
I got cluster validation to run only from Node04. I can't tdo it from Node03.
Here is what was in the report. It failed.

DHCP status for network interface Node03.domain.com - MY LAN differs from network Cluster Network 1.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.