none
Window has detected an IP address conflict.

    Question

  • Windows 7 / Dell XPS 9000 / Hard Wired ( NO hub or wireless )

    I keep getting an error that reads.

    Another computer on this network has the same IP as this computer. Contact your network administrator.

    I have contacted them and we have reset IP address checked pc setting installed new modem and I still get the error.

    I have empted dnc cache cleared all histories unplug and restarted

    PC setting are to acquire IP automatically

    Friday, October 21, 2011 3:06 PM

Answers

  • Sounds like the conflicting machine is only on the network intemittently.  During a period when you ARE getting the error message try this...

    1. Run ipconfig in a command prompt window on the complaining machine and determine the IP address.

    2. Now, turn that machine OFF.

    3. Go to another computer on the network and run "ping IP_address" in a command window. 

    4. A respone means that the conflicting machine is REALLY THERE ON THE NETWORK

    5. Go find it!

    • Proposed as answer by Thefazu Monday, October 31, 2011 5:09 AM
    • Marked as answer by Miya YaoModerator Thursday, November 03, 2011 3:10 AM
    Sunday, October 30, 2011 8:11 PM

All replies

  • Sir, try to get new ip address by :

     

    Start --> Run... ---> CMD

     

    ipconfig /release

     

    ipconfig /renew

     

     

    Regards,

     


    MCP | MCTS | MCITP
    Friday, October 21, 2011 3:35 PM
  • Windows will detect IP conflicts by sending out a gratuitous arp.  If another machine on the network responds that it already has the IP in question, Windows will advise you.

    Most cases, you'll find that yes, when you receive this message, there is another host on the segment with that IP.  However, consider this...if you have a loop in your network (maybe by having two layer two switches connected to each other improperly), its possible that your machine will send and receive these types of messages to itself, thereby producing the same message, when in fact there is no conflict of IP.


    Guides and tutorials, visit ITGeared.com.

    itgeared.com facebook twitter youtube
    Friday, October 21, 2011 5:43 PM
  • I tried this last night and I still have the error today.

    Any other ideas             

    Thanks

    Saturday, October 22, 2011 2:22 PM
  • I only have one machine hooked up and it has ran great for a year plus this has just showed up.

    Saturday, October 22, 2011 2:26 PM
  • Hi 36chevy,

    Is it a domain-joined computer? Or a stand-alone one?

    Try change the computer name and see the result.

    Regards,

    Miya


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, October 25, 2011 8:55 AM
    Moderator
  • Still need some help it came back after a day just can't figure this out!!!
    Sunday, October 30, 2011 7:06 PM
  • Sounds like the conflicting machine is only on the network intemittently.  During a period when you ARE getting the error message try this...

    1. Run ipconfig in a command prompt window on the complaining machine and determine the IP address.

    2. Now, turn that machine OFF.

    3. Go to another computer on the network and run "ping IP_address" in a command window. 

    4. A respone means that the conflicting machine is REALLY THERE ON THE NETWORK

    5. Go find it!

    • Proposed as answer by Thefazu Monday, October 31, 2011 5:09 AM
    • Marked as answer by Miya YaoModerator Thursday, November 03, 2011 3:10 AM
    Sunday, October 30, 2011 8:11 PM
  • how is it setup? domain network?

    Are the Ip addreses assigned by dhcp?

     


    Sravan
    Monday, October 31, 2011 5:33 AM
  • I am having the same issue at my work with several computers (All Windows 7 Pro).  These computers are all connected to the domain and connected via a wired interface.  After checking DNS I see there are no duplicate entries for the IP address in question.  Any ideas from anyone?  It does not affect the users performance or functionality but I get calls every time it happens.
    Thursday, December 15, 2011 5:04 PM
  • I have a similar problem ("Window has detected an IP address conflict") that has emerged only after a new Macbook joined my home network. In addition, the new Mac loses its connection if there are 4 or more other computers connected. I have a Netgear modem/router with 4 ports, but all computers connect wirelessly and my understanding is there's no limit on the number of wireless connections. But is there a limit to the number of IP addresses that can be or actually are allocated?

    Using ipconfig or ping is all well and good on the PCs on the network, but what's the equivalent for the Apples? If the solution is to manually set the IP addresses on the Macs, how is this done? And how do I set the IP range on the Netgear (if I need to)?

    Thursday, March 22, 2012 12:24 AM
  • I can not believe all the non-answers about this. Ok, so is step 6, take a twenty pound sledge hammer to the conflicting machine and bash it to pieces? Is this really a problem? I get it too and so far have not found anyone with any kind of sure answer. Is Microsoft so stupid that they can not say this is what this is and here is exactly how to fix it? No, as usual, you get a cryptic message and left scratching your head in wonder. Typical Microsoft.
    Saturday, July 07, 2012 10:52 PM
  •   It has nothing to do with Microsoft. DHCP works at the network level (which is why a Mac joining the network caused a problem for Harry). DHCP is a pretty simple-minded process. When a machine starts up it broadcasts a request and DHCP replies with an offer. It normally will not offer an IP which is already in use, but there are lots of things which can go wrong. As has been suggested you can prevent this by manually configure all your IP addresses, but this can get tedious if you have a lot of them (which is why DHCP was designed in the first place).

     The message is just a warning that two machines on the network have the same IP address (which may cause networking problems). As suggested above, doing an ipconfig /release followed by ipconfig /renew should get you a new IP address (which hopefully will not be duplicated). The only real solution is to check the IP address of every device on the network (not just the computers. Routers, printers etc also have IP addresses).

     

     

    Bill

    Saturday, July 07, 2012 11:36 PM