Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 348
  • Last Modified:

Conflicting IP Address

One of my servers is falling over due to an IP address conflict.

If I shut down the server, I can ping the address. But not sure what it is. Have tried to browse via HTTP and remote desktop.
How do I tell what the IP address belongs too?
5 Solutions
It might be a device other than computer. When you have opportunity can you;

ping youripaddress -t
 turn the remote switches one by one off and observe when ping stoppping.

Also you can use the following very useful, free tool which scans the network and give a lot of details.

You could ping and then tray an arp -a at the command prompt.  This should give you the mac address which can be searched on each switch by viewing the mac table on the switches.
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.

I would also use ping IP and then the arp command (suggested by penguinjas).

But then I use a lookup on the MAC address to see which company made the device.  Every MAC address has a Vendor part to it, so, for example, using the MAC address may tell you that it is made by Buffalo.  Then it may be quick to find any Buffalo devices on your LAN.
This is one website that has a lookup for MAC address to Company/Vendor.
Download this tool: http://www.nirsoft.net/utils/fastresolver.html
Usage instructions are also included in the site.
Make sure to install and run it using an account with admin privileges.
Curious, what is the IP of the server. You may be able to fix this issue, but if you are using the default 192.168.1.xxx schema, then you have a vulnerability which exists and can be recreated again and again. If you are using the 192.168.1.xxx schema, then I recommend changing it to a 10.0.0.xxx schema to avoid future conflicts. This map appear to be a pain, but in the long run you will increase your operational control of the network and prevent this issue from reoccuring. I bet that IP conflict is causing packets of data to not reach the server and making connectivity poor between the clients. Reacting to the problem is good, but finding and resolving the root cause is also just as important. Good luck on a swift solution.

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. 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