IP Conflict

G

Guest

In a 3 pc home network all running XP SP2, one of the PCs comes up
with a message: IP conflict with another address on Network.

No so as far as I can tell. The router shows consistent parameters for
the required IP range and all PC's have the same installation
parameters. If not through the router, how do I find IP addresses to
locate this so called conflict and resolve it?

Thanks for the help.

New Guy
 
N

Nil

In a 3 pc home network all running XP SP2, one of the PCs comes up
with a message: IP conflict with another address on Network.

No so as far as I can tell. The router shows consistent parameters
for the required IP range and all PC's have the same installation
parameters. If not through the router, how do I find IP addresses
to locate this so called conflict and resolve it?

IPCONFIG in a command session to see.

Control Panel | Network Connections | the connection in question |
General | TCP/IP | Properties to change. You probably want everything
to use DHCP by using the "Obtain an IP address automatically" option.
 
B

Brian A.

In a 3 pc home network all running XP SP2, one of the PCs comes up
with a message: IP conflict with another address on Network.

No so as far as I can tell. The router shows consistent parameters for
the required IP range and all PC's have the same installation
parameters. If not through the router, how do I find IP addresses to
locate this so called conflict and resolve it?

Thanks for the help.

New Guy

In simple terms:

That means the IP address it is trying to use is already being used by one of the
other two PCs. A common cause for this is when any or all of the PCs are shut down
and the IP isn't released. When the PC that failed to release the IP is rebooted, it
will have a conflict with any other PC that was re\assigned the same IP. Since the
PC that didn't release its IP wasn't booted yet, the DHCP server doesn't see that IP
as in use and assigns it to any other machine.

If you set the IP range in the router at 2-3 higher total IPs than the number of
PCs on the network, it will help prevent this from occurring. Once you set the range
higher, save the configuration and exit the routers web based configuration:

Shut down the machine(s).
Pull the power from the router.
Pull the power from the modem.
Wait approx 30 secs.
Apply power to the modem and wait for it to finish synchronizing with the cable.
Apply power to the router and wait for it to finish synchronizing with the modem.
Power up the machine(s).
The machine(s) should now be assigned a new IP from the router.


--
Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
G

Guest

Seems logical. It is only one of tye three that behvies this way. seem
unusual. I will give it ta tryl

Thanks.

New Guy
 
G

Guest

Sorry for the delay...tried your approach, seemed to work, then
problem came back.

Something happened to screw up my setup...a KVM switch keyboard
connection came lose and both computers tried to reboot and got hung
no finding a key board. Didn't recycle the modem and router and the
problem is back.

Only one of the two has the problem of IP conflict and all ranges and
IP addresses are within the same ranges. If one sees a conflict, why
doesn't the other??

Thanks for the help.

Henry
 
B

Brian A.

The one sees the conflict because it's trying to use an IP address that's already
assigned and in use. The other doesn't see it because it's already using the IP
address. The conflict will only be reported for the one that's attempting to use an
IP address that has already been assigned to and in use by another PC.

To check the assignments per PC, on each PC open a cmd prompt and type ipconfig
/all.

Click Start > Run and type in: cmd and press Enter or click Ok.
At the cmd prompt type in: ipconfig /all *note the space before /all*

--


Brian A. Sesko { MS MVP_Windows Desktop User Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
M

midearmon

The one sees theconflictbecause it's trying to use anIPaddress that's already
assigned and in use. The other doesn't see it because it's already using theIP
address. Theconflictwill only be reported for the one that's attempting to use anIPaddress that has already been assigned to and in use by another PC.

To check the assignments per PC, on each PC open a cmd prompt and type ipconfig
/all.

Click Start > Run and type in: cmd and press Enter or click Ok.
At the cmd prompt type in: ipconfig /all *note the space before /all*

--

Brian A. Sesko { MS MVP_Windows Desktop User Experience }
Conflicts start where information lacks.http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

Hello,

I had something similar, but I found the machine. When I found it I
checked the IP of the conflicting machine and the IP was different.
The IP of the machine i needed was 135. The conflicting machine was
35. So I changed it to 36. I got the same thing. So I unplugged it
to check it for sure, and sure enough the confliction went away.

We have a static network, about 80 machines. Is there any reason it
would cause a IP confliction with a machine that has a different IP?
Sounds bogus to me, but it's played out that way, clean.

Thanks in advancee,

Mike.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top