10/100 disables secondary gigabit switch.

[Andrew Ellis]

Hello,

I have just finished setting up my home network. The modem is a Comcast modem set to Bridge Mode. So from LAN 1 to the TP-Link OnHub is how I have our wireless network configured.

From the OnHub I have a Cat6 cable running to LAN1 on a TP-LINK TL-SG105 (we will call this Living Room) Gigabit switch. From Living Room LAN2 I have a Cat6 running to another TL-SG105 (we will call this Office) on LAN1.

Living Room LAN3 goes to my Xbox One. Living Room LAN4 goes to my Drobo5N.

Now the problem I am having is when I connect my Sony 65x850D to Living Room LAN5, it is running at 10/100 while LAN1-LAN4 are running at 10/1000. That seems fine, but this causes Office to fail to assign network addresses over DHCP.

Office reports LAN1-LAN3 running in 10/1000, but I am unable to connect to the internet on any device on Office.

When I disconnect the TV from Living Room LAN5, all connections on Office start to operate normally.

Why would the TV running on 10/100 bring the secondary switch to its knees?

Cheers,
Andrew

 

[abailey]

Two things I would check would be the cable going to the TV. Try a different ethernet cable. Second, is your TV assigned a static IP? If so make sure it does not conflict with other IP addresses, including those handed out by DHCP.

 

[Andrew Ellis]

Nothing on the network is static, maybe I'll try manually assigning static IPs to all wired devices and see if that helps.

I tried three different Cat6 and two Cat5e cables and the same result happens; so it's for sure not the cables.

 

[nigelivey]

The adapters are auto sensing the speed and duplex, when there is a mismatch things can get messed up. Can you manually set speed and duplex on the TV or the device it is connected to? tr making them match. Also check the TVs IP settings.

 

[Andrew Ellis]

So setting the IPs of all devices in the network to static IPs resolved the issue. Not exactly sure which devices we're fighting over DHCP reservation, but that appears to have been the problem.

 

[nigelivey]

So setting the IPs of all devices in the network to static IPs resolved the issue. Not exactly sure which devices we're fighting over DHCP reservation, but that appears to have been the problem.

If nothing is set to static, there is no fight over IP addresses, the problem will be elsewhere.