Domain Controller has an IP conflict

I was uninstalling symantec endpoint this morning to replace it with kaspersky. Logging in after reboot I see an IP conflict message. I checked the DHCP leases and I don't see this IP in use anywhere. Our DHCP runs on Windows 2008 R2 and this domain controller is Win08 R2. Any ideas?
Who is Participating?
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.

Trent SmithCommented:
Sounds like you have a static address.  You can download Advanced IP Scanner to see if the address is truly being used.  It might also give you an idea of what is using it.

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
Paul MacDonaldDirector, Information SystemsCommented:
I can't tell if you're suggesting your DC has a NIC that's DHCP, or if your DC's IP address isn't reserved in DHCP, but if either of those is true you have other issues.

That said, is it possible the DC is multi-homed (has more than one NIC) and has been configured with the same IP address on both NICs?
stlhostAuthor Commented:
I should of said the NIC has a static IP address, sorry about that. It only has one nic.  There are no reservations. I will scan the network and see if anything comes up with that IP
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

DeepinInfrastructure Engineer Commented:
I would check the DHCP scope as well, if your using the full range x.x.x.1 - x.x.x.254 narrow your DHCP scope eg x.x.x.10 - x.x.x.254 exclude your servers as you have already assigned a static IP or Exclude your servers within DHCP
stlhostAuthor Commented:
The range isn't to large, rest are excluded just not the domain controllers IP when it should be.
stlhostAuthor Commented:
Believe it or not this worked. I turned off that DC for a little bit and started to ping it and it came up as Texas Instruments. Turns out our DVR system grabbed that IP
David Johnson, CD, MVPOwnerCommented:
always always assign a reservation for static ip's
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.