In windows, new machine does not capture the IP address and its ethernet does not work until the old machine is rebooted, also there is a pop up to alert the IP conflicts on both the machine. event is also logged with the conflicting mac address..

regards
anil


Bret Hughes wrote:
On Wed, 2002-08-07 at 23:04, bindal wrote:
In RH 7.2, when a PC is configured with an IP Address on a LAN and that 
IP is already configured on another machine, then the new machines grabs
the IP from the old machine and causes the malfunctioning of the old PC
with the same IP..

This way anyone can bring down our server on our LAN ??

And there is no way to know if there is an IP conflict ??

Any solutions to this problem ??

I don't think so, requiring dhcp helps since the ip addresses are sure
to be seperate. It can be a real bitch to figure out what is
happening. I personally misconfigured a machine using a used ip address
and thought that the interface did not come up after the change since I
could not get to it. turns out that every now and then the arp table
would ask who has this ipaddress and whichever one answered first would
be the one I would get to. I spent about four hours solid trying to
figure out what happened. I finally got into the box and was able to
change the address.

BTW I don't think this is a linux only issue. I believe you can set up
a windows machine with a wrong ipaddress too and the interface will come
up but I have not tested this.

I looked around for a patch to the networking code that would check to
see if a machine on the lan answered an arp "who has ip blah blah " but
the only one I found was said to be buggy so I punted, went to dhcp on
all our nets and have not looked back. This was over a year ago so the
situation may have changed since then.

Bret







Reply via email to