this feels like a network issue. Am I correct that Google Wifi is not your home router?
If this is correct, can you check if all devices (especially the ones connected by Google Wifi and the ones on the home router) have the same IP range?
In many cases the default IP range is 192.168.0.x (and only the last number, represented by the x, should be different on each device)
Hi @Jason_Gogal ----- Thank you for the report and sharing your feedback with us. The insight is appreciated! Sorry to hear of the troubles.
Moving forward, to “piggy back” on the suggestion made in @crieke’s post above (), you can also try an app like FING to scan your network looking for devices that it can “see”, showing itself in the process.
As you can see from your screenshot, , the DHCP server in the Google Wifi device will give out IP addresses in the range 192.168.86.0/24 - and it’s not changeable. If your router has a DHCP server giving out addresses in the 192.168.172.x range, then this is a different address space. The two networks are totally separate.
I think the best solution is to disable one of the two dhcp servers. I am currently studying the manual of the Actiontec V1000H.
It should also be possible to deactivate the DHCP server on the Google Wifi, but it is not recommended by Google…
@Jason_Gogal: Is it possible to connect all ethernet cables directly to the Google Wifi devices (maybe with a simple network hub/switch)?
Sounds like a good idea (if it is doable).
If nothing else is connected to the ActionTec V1000H, you could also think about using this device only as a modem and establish the connection to the internet (VDSL2?) directly by Google Wifi.
I’d also recommend to save your config files from all involved devices on your computer, so you will be able to revert back easily to the current config.
Then my guess is that the ActionTec has nothing to do with your internet connection.
You could try it by connecting a computer directly to the fiber modem. Eventually you have to reboot the fiber modem if you connect a different device to it, as the fiber modem might lock to a specific Ethernet MAC address (this is also the case with my cable modem). If that works, I’d connect your fiber modem directly to the WAN port (the one that has the Globe icon) of your Google Fiber Base.
I currently see no reason to keep the ActionTek device in your network chain…
I rerouted all the devices through the outbound port of the google wifi. Then I found that my NAS was bricked. So I plugged its second ethernet port into the router and made both of its ports static. Now everything that matters is on the 192 network and I can control the Shield endpoint running Roon from the NAS from my iphone. I assume it will also work from my tablet now.