Once upon a time, probably 4 or 5 years ago we had a computer that we joined temporarily to our network with an IP address of 10.0.1.20. That computer was a thin client that we were using for purposes of testing with a name of neo-6381bd. The computer in question has not been connected or used on our network in probably 4 to 5 years.
Now we are adding a new server to our network that we have setup with an IP of 10.0.1.20. However in this case the computers name is elastix. However when we scan our network to see what computers are available the IP address 10.0.1.20 still shows that its name is neo-6381bd. I have gone into active directory and removed neo-6381bd from the list of computer and added elastix. However this did not fix how the computer is listed. The software we set the server up to host is not working because of this name conflict.
What would I have to do to get this computer to show up in the list of computers with the correct name?
You probably have a stale A record in your DNS that still points to that old machine. The machines will register themselves to DNS, however they will not be removed.
Open up DNS on your domain controller
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008.
Determine the location of the FSMO roles by lo…
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…