Devices connected by ethernet switch to Google Wifi AC1200 not working

[nrmaharaj]

Apologies if this is already covered: searching keyword "ethernet" didn't turn up a similar issue.

So here's my situation:

Until about a month ago (?) the router + 2-mesh point setup below was working fine with all wired devices happily getting internet through their wired connections. What tipped me to a problem was when devices such as my TV and AV receiver, which can only be connected by ethernet, stopped being accessible through their apps (I confirmed in the Google Home app that they're no longer on the network at all).

So here's my router + 2 mesh point setup:

modem ➡️ Google Wifi AC100 puck configured as router ➡️ 40 ft. ethernet cable ➡️‌ 8-port TP-Link switch ➡️‌ short ethernet cables to assorted entertainment devices 📺📻🎮

+

TP-Link Google OnHub mesh point ➡️‌ 5-port TP-Link switch ➡️‌ 2 desktop PCs 🖥‌🖥‌

+

TP-Link Google OnHub mesh point ➡️‌ Lenovo dock ➡️‌ 1 laptop computer 💻

What I've done

1. Unplugged ethernet cables from all devices and factory reset the network.
2. Confirmed in the Google Home app that wifi-capable devices with ethernet also connected (eg. Chromecast) are using wifi for their connections in the Google Wifi puck's router chain.
3. Confirmed in the Google Home app that wifi-capable devices with ethernet also connected are using ethernet for their connections in the first Google OnHub's mesh point chain. 
4. Swapped the 2 switches to see if the 8-port one was broken, despite happily-blinking lights. Switch works when connected to the OnHub, and the switch that was working with OnHub fails to provide connection when connected to Google Wifi
5. Connected directly to the Google Wifi puck's ethernet port. Direct ethernet connection works ✅
   1. Despite this, assuming the long cable was the problem, I've also replaced the long ethernet cable between the wifi puck and the 8-port switch.

So it seems like there's an advanced setting in the Google Wifi router that needs to be set to allow devices to connect through a switch. I just don't know what that might be.

[Juzdu]

I don't think I have a solution, sorry...but did want to mention I do the exact same thing with my Nest Wifi Router.  I run an ethernet cable out to an 8-port Tenda (SG108) switch, then run cables to a heap of my entertainment equipment.  I also run a cable from the 8-port Tenda into a wall point that then runs up to the other end of my house, where I have a 5-port Tenda switch that feeds my main PC and a couple other wired devices.  It's all been working ok for a couple of years now.

So what you're doing is obviously correct, but something's broken somewhere.  I don't know anything about OnHub, but I heard late last year that Google was dropping support for them in 2022. 

[nrmaharaj]

Yeah, the OnHub news is why I moved things around to make them just mesh points, rather than relying on one as a router (they'll keep working, but won't get updates--so I put them where they'll least need to be updated). Ironically, ethernet connected to the OnHubs works perfectly. It's the Google Wifi puck that's misbehaving.

[Juzdu]

This one is frustrating me.  The fact your hardwired ethernet device works when plugged directly into the Nest wifi router, but not when the router runs to your switch first is really strange.  The TP-Link switches are definitely 'dumb' switches yeah, not devices with a WAN and multiple LAN ports?

[nrmaharaj]

That's right. Totally dumb switches that were 100% plug and play for over a year (and still are when connected to a mesh point).

[nrmaharaj]

An update: it works now. I can't tell you why. Possibly power-cycling with all ethernet cables unplugged, then reconnecting them in some specific sequence was finally agreeable to the router. So all I can say to others with this problem is, don't lose hope!

[Juzdu]

Good to know, that was annoying me given there was no reason it shouldn't work! Glad you reported back.

[Jeff]

Hi, nrmaharaj.

Thanks for letting us know what worked for you. It's been a while since this was wrapped up, so I thought I would check in and see if anyone needs anything else or if we're good to mark this as resolved. If anyone needs anything else, just let me know.

Thanks.

[Jeff]

Hi, everyone.
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks.

[Jeff]

Hi, everyone.
As we haven't had any activity here recently I'm going to go ahead and close the thread. If you have more to add, feel free to start a new discussion.
Thanks