Solved

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

Posted on 2013-11-26
2
859 Views
Last Modified: 2013-11-26
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.
0
Comment
Question by:MEATBALLHERO
2 Comments
 

Author Comment

by:MEATBALLHERO
Comment Utility
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
 
LVL 5

Accepted Solution

by:
warddhooghe earned 500 total points
Comment Utility
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

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Companies that have implemented Microsoft’s Active Directory need to ensure that the Active Directory is configured and operating properly. If there are issues found and not resolved, it eventually leads the components to fail or stop working and fi…
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now