[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 853
  • Last Modified:

Old Computer names not purging from Network

I have renamed PC's to reflect the USER name for the workstation in Active Directory on a Windows Server 2003 Network but when I run an angy ipscan on the network it still shows the old Computer names on most of the PC's.  I also have the same issue when I look at the status of the PC's in Kaspersky Admin Kit.  How can I stop these old names from reappearing?  

One note, the ipaddress are not affected.
0
IgaravidezK
Asked:
IgaravidezK
1 Solution
 
wdurrettCommented:
This is probably due to DNS entries.  You can go into your DNS server and delete all the A records for the old machine names.

0
 
Hypercat (Deb)Commented:
Before you do that, however, make sure that you see DNS entries for the new machine names, otherwise your user may experience some connectivity issues.  If the new machine names don't show up, either reboot them or go to each machine, open a command prompt, and type:
ipconfig /flushdns
ipconfig /registerdns
 
0
 
ARK-DSCommented:
DNS Scavenging is the answer to your problem. Scavenging goes ahead and deleted all stale (unused) entries from the DNS automatically for you.
You need to be very precise and carefull while configuring the scavenging and then a little patient for it to happen as it waits for a specific period of time to delete the stale records.

See this t oknow how to configure scavenging:
http://blogs.technet.com/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

Regards,

Arun.
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
peakpeakCommented:
Also check your WINS entries.
0
 
Hypercat (Deb)Commented:
DNS scavenging does work well, but it's a little bit tricky to configure. Unless you have a lot of workstations, and unless you add/remove workstations, change names and/or change IP addresses frequently, there's not a huge benefit to configuring scavenging.
0
 
IgaravidezKAuthor Commented:
I have done all the above except for running ipconfig /flushdns, ipconfig /registerdns

I still get old entries when running an ipscan even though I deleted the A records.  I did not want to try Scanvenging but will leave it as a last resort.  Also, where do I go to check the WINS entries.

Thanks
0
 
Hypercat (Deb)Commented:
You may or may not be running WINS on your network.  If you configured the network yourself and didn't specifically install and configure WINS, then you don't have it running.  It's not necessary with Windows 2003 Server/Windows XP or newer operating systems.
I'm not sure what the IPscan app does, as I've never used it.  If you use regular network browsing, do you see the old computer names or the new ones? Are you have any communication/browsing issues on your network?  If you look in AD Users and Computers, in the Computers container, do you see the old or new PC names, or both?
0
 
IgaravidezKAuthor Commented:
IPscan scans network for any ip address in a range chosen.  New computers are the only ones in AD computers.  I am not having communication issues but can not tell which machines are having issues as they are not showing the new computer only the old names.
0
 
Hypercat (Deb)Commented:
Check your DNS reverse lookup zone to be sure that there aren't old PTR records in there. If so, delete them also.
If I'm understanding you correctly, when you go to AD Users and Computers, the new computer name appear, but when you browse the old names appear.  Is that correct?  On one of the workstations, if you go to the System properties, on the Computer Name tab, and click Change, what do you see for the Full computer name listed there?
0
 
IgaravidezKAuthor Commented:
All the computers are correct on AD COMPUTERS as well as the COMPUTER NAME tab.  When I am trying to get an inventory with any third party software or pinging the network range (i.e. WHATSUP GOLD, IPSCAN, BELARC), I still get old computer names.  I will check the DNS reverse lookup zone tonight and give you an update.
0
 
IgaravidezKAuthor Commented:
Thank you Hypercat, the DNS Reverse Lookup Zone was the answer
0

Featured Post

Has Powershell sent you back into the Stone Age?

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.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now