Ping by name returns the wrong IP address

I slipped and did a big networking NO NO. I recently restored a backup of a ghost image on a computer. Somehow it slipped passed me and I connected it to our network, when the original computer was still on the network. The orginal computer is setup with a static IP address (since it's a server), therefore the restored machine was also static IP address, SAME IP ADDRESS, SAME HOSTNAME. Anyways, bells and whistles went off on the original computer when the network found the duplicate IP/Hostname, which then I disconnected the restored PC from the network. Now, when I try to ping the original computer by hostname it returns an different IP address than the static one I've given it. When I try a ping -a XX.XXX.XXX.XXX, on the static IP address, it returns a different hostname. I know this is probably a DNS issue but I'm not exactly sure where to look.  I'm running DNS and DHCP on a Windows 2000 Server machine w/ Active Directory.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob WilliamsCommented:
Open the DNS management console and under Forward look up zones for your domain delete the A record for the computer in question, or correct it. In the reverse lookup zones (if you have them) look for the Ptr record for that IP and delete or edit it.
If using static IP's you should be OK but if you used DHCP briefly check the assigned addresses to make sure they are correct. Delete the wrong entry  if one exists.
Then on the computer from which you were making the query you may also need to run at a command line   ipconfig  /flushdns
This should help.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
try removing all the entries in your arp table

arp -d *

the try a ping to
Also reboot the machine in question  (or disable then re-enable it's networking) just to ensure it re-claims it's IP.  Once you're sure the machine is on the right IP run ipconfig /registerdns  which will cause it to update all it's records in DNS
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

I think rob has the answer here: check the DNS entries, and then do ipconfig /flushdns. quite likely the machie you are pinging from simply has it in the DNS cache. It has nothing to do with arp, since thats about mac-ip address resolution, not name resolution.

A reboot of the client machines will probably fix this too, so unless its affecting someone, just wait til they reboot.

Sam PanwarSr. Server AdministratorCommented:

Have you check your local system etc/host file entries

c:\windows\system32\driver\etc\hosts file there any entry remove it and try
linux in etc\hosts

HaradminAuthor Commented:
Thanks RobWill, that did the trick!
Rob WilliamsCommented:
Thanks Haradmin,
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.