Discussion Locked

IP Address Conflict!

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Recently I set up all the computers at my place of work to network print. In the process, I had to update the network card driver for one of the nodes.

Since then (last 2 - 3 days)I have been having constant messages appearing on my screen saying:

"Windows has detected a conflict for IP address xxxxxx with thsystem having hard ware address XXXXXXX"

Doing some PING-ing,the PC I use has that IP address and the other PC have their own IPs. One PC cannot be browsed on the network( the samePC I updated the driver for)

The network uses DHCP, yet it keeps happening
Rebooting the PCs doesn't help for long.

How do I end this problem? It is killing my work rate.

P.S.: I'm only A+ certified, s I only know basic networking so breakdown the answers where you can.

7 replies

by gutridgesj

sounds like some pc is not using dhcp and has a static ip address and then when the other pc tries to be assigned an ip using dhcp, the ip is used.

the network does not use dhcp, the pcs do. which means unless all the pcs are set up to use it, any pc can do whatever it wants.

check the tcp/ip settings on the pc you changed the card and your pc to make sure it is not using a static ip.

on dhcp, unless there are a lot of pcs to deal with, say more than 100, i would not even use dhcp.

by for7676

try removing TCP/IP from the system, restarting, and reinstalling TCP/IP. This would re-bind the protocol to the adapter, and could resolve your issue.

by mphoffar

There's something out there using the same IP as you are. I'm with the guy in answer 1, in that there's probobly someone set somewhere with a static in one aspect.

One side I may look at is what is happening with your leases. You may be able tojust run winipcfg, release the IP and then renew a new one from the DHCP server.

This may also be something resulting from the MAC address or the computer name. I would probobly just reload the entire stack with a new computer name and see if the prolem resulves itself from there.

Good luck to you

Mark

This discussion is closed to new replies.