Originally posted by: Goosemaster
Originally posted by: Ynog
Originally posted by: BeanDip
If you are on the same network such as 192.168.0.x but none of the PCs have duplicate IP addresses then they will merge and be one big happy family.
If any of the PCs have duplicate IP addresses then you will have conflicts.
I kind of figured there would be conflicts, but what problems arise from these conflicts.
Thats what I am looking for.
Actually, windows MIGHT...as in MIGHT allow the FIRST machine with a duplicate IP to stay on the switch and communicate with PCs that have different IPs. Other IPS that are the same as the first one will not be allowed on the switch. Keep in mind that this is a rare occurance.
Usually, duplicte IPs will prevent all machines with dup. ips from transfering at all....basically, the arp will return be getting the other PC's IP and your own as well....no good.
Sorry for the late response.
Ok so dupilicate IP will prevent all machines with dups from transfering.
But what behavior might be expected in this case.
Two machines (A1 and A2) are connected through a switch (S1) on Lan A.
Two more machines (B1 and B2) are connected through a separate switch (S2) on Lan B.
The machines (Linux) are all booted, and get IP and communicate with each other ok (A1 to A2) (B1 to B2),
because they are separate networks.
Now my question arises is if Lan A and B are then connected, where A1 and B1 both have the same IP,
What behavior will result? I realize that ARP packets will go out. But I am not sure how the switch will
effect the situation. Will A1 bump B1 on LAN B and B1 do the same on A1's LAN?