IP conflict

[Bituser]

Hello,

I am having trouble setting up ICS with my home network. I have uploaded a diagram I made to better explain what I am meaning.

What I have done on my laptop is bridge my wireless connection with my lan port so my computer next to the laptop can connect to the network and internet. It's working good as all devices are seeing each other and can connect to the internet.

My only problem is that the computer wired to my laptop can't be connected to when I turn it on sometimes because of a IP conflict. I have tried setting static IPs for the bridge and for the wired computer but I just can't get them to communicate once I have done that. It appears to be a simple solution, but I can't work it out :sarc:.

The computer connected to my laptop is running Windows XP professional, the laptop is running Home Premium x64 and the topmost computer is also running Home Premium x64.



Thanks Guys,

Bituser - Sam

 

[zigzag3143]

Hello,

I am having trouble setting up ICS with my home network. I have uploaded a diagram I made to better explain what I am meaning.

What I have done on my laptop is bridge my wireless connection with my lan port so my computer next to the laptop can connect to the network and internet. It's working good as all devices are seeing each other and can connect to the internet.

My only problem is that the computer wired to my laptop can't be connected to when I turn it on sometimes because of a IP conflict. I have tried setting static IPs for the bridge and for the wired computer but I just can't get them to communicate once I have done that. It appears to be a simple solution, but I can't work it out :sarc:.

The computer connected to my laptop is running Windows XP professional, the laptop is running Home Premium x64 and the topmost computer is also running Home Premium x64.
View attachment 150093


Thanks Guys,

Bituser - Sam

Great post. I do have one idea. Is the networking set up to use Homegroup (IPV6) or workgroup (IPV4). Homegroup is for win 7 networks, workgroup for mixed with older hardware.


Ken

 

[Kari]

If you do not set static IP's to all devices, then you need to choose those IP's used as static from the end of your IP pool. If for instance you are using normal 192.168.x.x range, use IP's like 192.168.x.250 to 255.

When devices using dynamic IP's get their address from DHCP server, they usually get addresses starting from the low end of your IP pool. So, if you have several dynamic IP devices on and connected and you then boot a device whose static IP is from the low end of the address pool, the conflict is almost sure to happen.

Better of course would be to use only static addresses.

Kari

 

[Bituser]

Hello,

I am having trouble setting up ICS with my home network. I have uploaded a diagram I made to better explain what I am meaning.

What I have done on my laptop is bridge my wireless connection with my lan port so my computer next to the laptop can connect to the network and internet. It's working good as all devices are seeing each other and can connect to the internet.

My only problem is that the computer wired to my laptop can't be connected to when I turn it on sometimes because of a IP conflict. I have tried setting static IPs for the bridge and for the wired computer but I just can't get them to communicate once I have done that. It appears to be a simple solution, but I can't work it out :sarc:.

The computer connected to my laptop is running Windows XP professional, the laptop is running Home Premium x64 and the topmost computer is also running Home Premium x64.
View attachment 150093


Thanks Guys,

Bituser - Sam

Great post. I do have one idea. Is the networking set up to use Homegroup (IPV6) or workgroup (IPV4). Homegroup is for win 7 networks, workgroup for mixed with older hardware.


Ken

Thanks for the compliment and the Rep Ken . I thought I would get more replies if I properly explained . I didn't know about that minor difference with Homegroup and Workgroup, you can have some rep too .

If you do not set static IP's to all devices, then you need to choose those IP's used as static from the end of your IP pool. If for instance you are using normal 192.168.x.x range, use IP's like 192.168.x.250 to 255.

When devices using dynamic IP's get their address from DHCP server, they usually get addresses starting from the low end of your IP pool. So, if you have several dynamic IP devices on and connected and you then boot a device whose static IP is from the low end of the address pool, the conflict is almost sure to happen.

Better of course would be to use only static addresses.

Kari

Thanks Kari. I switched all devices that supported static IPs to static and was still having the same issue. I found the solution though. I completely forgot about setting the DNS servers :shock: +Rep

Thanks for everything guys, glad I have this sorted

~Bituser - Sam

 

[Kari]

Good to hear you got it sorted.

Kari