?
Solved

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

Posted on 2013-11-26
2
Medium Priority
?
906 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 

Author Comment

by:MEATBALLHERO
ID: 39679512
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 2000 total points
ID: 39679564
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

Ransomware Attacks Keeping You Up at Night?

Will your organization be ransomware's next victim?  The good news is that these attacks are predicable and therefore preventable. Learn more about how you can  stop a ransomware attacks before encryption takes place with our Ransomware Prevention Kit!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
A hard and fast method for reducing Active Directory Administrators members.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…
Suggested Courses

764 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