IP Conflict

  • Thread starter Thread starter Bob Eyster
  • Start date Start date
B

Bob Eyster

I have been getting this error off and on for a couple of weeks.

Error: There is an IP confict with another system on your network.

I have a 3 PC and 1 printer networked receiving IP address by DHCP from my
Linksys router. I also have a 1394 Connection which has been disabled.

Is there any way to find out what is conflicting with what???


Thanks
Bob Eyster
 
Bob Eyster said:
I have been getting this error off and on for a couple of weeks.

Error: There is an IP confict with another system on your network.

I have a 3 PC and 1 printer networked receiving IP address by DHCP from my
Linksys router. I also have a 1394 Connection which has been disabled.

Is there any way to find out what is conflicting with what???

there are only three PC, so you can do an IPCONFIG command and show their
configuration.
Can you post the result here?
Bye
 
On the Linksys router, you should be able to "see" which IP addresses are
assigned.

You need to check each PC so as to "see" the IP address that they have
received. You also need to check the printer.


Each networked device MUST have a unique IP address on the network.
 
start>run>cmd
at command prompt type: ipconfig /release
at command prompt type: ipconfig /renew

did this on computer with modem and router
probaly have to do on computer w/failed connection
 
Bob Eyster said:
I have been getting this error off and on for a couple of weeks.

Error: There is an IP confict with another system on your network.

I have a 3 PC and 1 printer networked receiving IP address by DHCP from my
Linksys router. I also have a 1394 Connection which has been disabled.

Is there any way to find out what is conflicting with what???


Thanks
Bob Eyster

Printers do not normally use DHCP. They most often have a fixed I.P.
address assigned, so that is probably where the conflict arises.

Check the documentation for the Linksys router. Usually the DHCP
server only uses a range of 100 or i.p. addresses out of the 256 total
available (000 to 255).

One solution would be to assign the printer a different i.p. address,
one that is outside the range used by DHCP.

Another option that might be available via the internal configuration
settings of the Linksys router (see the documentation for instructions
on accessing this) would be to configure the DHCP server so it does
not allocate the specific i.p. address being used by the printer.


Another possibility would be if you are using a wireless router and
one of the PCs is at or near the range limit for your wireless
hardware. This limit can be as little as 40 to 50 feet depending on
the hardware and on the construction of the building. If a PC is
connected by wireless and the connection is dropped temporarily
because of communication problems then it is possible that DHCP would
reassign that computer's i.p. address to another machine. Then when
communication was re-established to the first machine it would think
that it still had a valid lease on that i.p, address and would try to
use it, thereby creating the type of error that you describe.

I have seen this second type of situation actually happen several
times, but I think the printer i.p. address is the more likely
suspect.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm
 
Good advice from the pros if you want to use DHCP.
In the Linksys DHCP setup, make sure it is set to allow at least as many
addresses as you have devices.
Linksys router address 192.168.1.1
default user id = blank
default p/w = admin
I change both.

To permanantely eliminate the problem, you could assign fixed IP addresses.
For example, you could use
PC1 192.168.1.101
PC2 192.168.1.102
PC3 192.168.1.103
Printer 192.168.1.104
All set to use gateway 192.168.1.1
subnet mask 255.255.255.0 is standard, you can make one up if desired, but
all have to match.
 
Thanks everyone for your replies.

I appeared it was the 1349 network causing the problem. When I disabled the
network I didn't reboot the PC. After doing so all seems to be working OK.
No IP conflict sence I posted the message.

Again Thanks
Bob Eyster
 

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

Back
Top