I have been trying to cast from my PC to Chromecast after I set up Google Nest Wifi with no luck so hopefully, someone could suggest a working solution.
Modem/Router 4 ports (192.168.2.1 gateway, 255.255.255.0) ->
Before: I was using the Modem/Router Wifi for everything and all worked except the signal was weak or non-existent in some parts of the house.
Now: the Wi-fi signal is awesome, however, I am no longer able to cast from PCs to Chromecast.
I tried changing Google Nest Wifi advanced network settings but it never saved them so not sure what to do.
Please suggest if you have any working solutions.
Nest Wifi by default acts as a NAT router, with a firewall, DHCP and an access point. Thus, if you could reach the Chromecast from a device connected to your modem, that would be similar to someone on the internet being able to reach your Chromecast. So, it's by design.
Either bridge your modem, and use Nest Wifi as a NAT router, connect everything to it. Or bridge the Nest Wifi puck, assuming you only have one and don't use its' mesh capabilities.
Thank you for your quick reply! The whole point of me getting Nest Wi-Fi is the mesh capabilities with 3 points (I had a single wi-fi router before).
On the "Bridge your modem option" I could not find the bridge on the modem (Home Hub 4000) however there is an Advanced DMZ option:
The advanced DMZ feature allows a device to use the modem's WAN IP address as its own. It also puts the device outside the modem's firewall. Your modem's WAN IP is: xx.xx.xxx.xx"
I entered google Nest Wi-fi MAC/IP in the Advanced DMZ option, and so based on what it says it should carry forward the outside IP to the Google Nest router.
Unfortunately, it did not make Chromecast visible from my PC.
Any other suggestions? Perhaps I could get another switch placed between the modem and Google Nest Wifi and plug all PCs into that switch. I could place the switch into the bridge mode. Not sure if that will do the trick though. Modem->Switch (bridge mode)-> Google Nest
If your modem can't be bridged (contact your ISP just in case), just run double NAT: Turn off modem Wifi and don't connect any devices to it by cable other than the primary/ master Nest Wifi. The point is that all your devices must be connected behind the same NAT router and firewall in order to talk to each other. If you need more ethernet ports, connect a switch behind the master Nest Wifi puck.
Thank you for your advice! I confirmed that the modem does not have a bridge mode.
I do like that my PCs are directly connected to the modem to minimize any potential latency. While wifi and media that kids are using are on a separate network. The only issue is that I occasionally need to cast from my work PC to Chromecast.
What I am going to do is buy a usb-wifi adapter and use it to connect to Google Nest wifi when I need to cast. I wish there was a good alternative to keeping both mesh capabilities and PCs connecting straight to the modem.
Well, I agree that Wi-Fi adapter is a patch, not a solution. There are other considerations though. The modem/router is in the basement and all 4 LAN cables are dropped to the basement from the main and 2nd floors. Google Nest Wi-Fi is connected to LAN on the main floor.
To do what you are proposing I would need to relocate Google Nest Wi-Fi to the basement (and I don't need Wi-Fi in the basement - it will be a waste of signal), buy a 4-way switch (since there is only 1 output on the Google router), and potentially add another Wi-Fi point on the main floor. It would be a better network architecture, but more costly than just a USB adapter. I was looking for a software solution just to cast to Chromecast rather than a full network re-work. I appreciate your suggestions though.
So I've got the TP-link USB ac1300 adapter, connected it to the Wi-Fi, and was able to cast to Chromecast as easy as 123. The Internet comes directly from the modem through a Gigabit port and I am also connected to Nest Wi-Fi and can see all devices there. Not sure if there are any downsides to running this double NAT thing but so far everything works flawlessly.
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.