05-06-2022 03:22 PM - edited 05-06-2022 03:23 PM
I have a Sagemcom router from my internet provider (YouSee) which I hooked a NAS drive to. After disabling Wifi on that router and switching to Wifi via a Google Nest mesh wifi, I can no longer reach the NAS drive on local ip. What can I do re-establish this connection? I am using the NAS as media storage and would like to be able to reach its shared folders from my laptop etc. when at home on the Wifi. The NAS also has game servers on it that has to be accessible from outside the local network so I'd rather not move the NAS to the Nest router.
Thanks in advance for any advice on this.
Answered! Go to the Recommended Answer.
05-07-2022 07:16 AM - edited 05-08-2022 05:32 AM
Hello @jesh
The Nest WiFi Router is also a firewall. So, it's creating a new "inner" network inside the one created by your Sagemcom router. This will limit the ways devices on the inner and outer networks can talk to each other. In particular, broadcast/multicast autodiscovery protocols will not work across those two networks. So, you won't be able to access the NAS using a hostname or a machine browser. But, if you know the IP address of the NAS on the outer network, devices on the inner network should be able to connect directly using that address, at least for file-sharing protocols. It would still be less complicated to have everything on a single network, even if that requires two layers of port mapping (from Sagemcom to Nest WiFi, and from Nest WiFi to NAS).
05-07-2022 07:16 AM - edited 05-08-2022 05:32 AM
Hello @jesh
The Nest WiFi Router is also a firewall. So, it's creating a new "inner" network inside the one created by your Sagemcom router. This will limit the ways devices on the inner and outer networks can talk to each other. In particular, broadcast/multicast autodiscovery protocols will not work across those two networks. So, you won't be able to access the NAS using a hostname or a machine browser. But, if you know the IP address of the NAS on the outer network, devices on the inner network should be able to connect directly using that address, at least for file-sharing protocols. It would still be less complicated to have everything on a single network, even if that requires two layers of port mapping (from Sagemcom to Nest WiFi, and from Nest WiFi to NAS).
05-08-2022 03:01 AM
Thank you for the explanation, @MichaelP. That helped and it did the trick when I replaced references to my NAS by the local ip instead of its hostname. That's good enough for my use so I'll stick with that setup so far.
05-09-2022 08:40 AM
Hi, jesh.
Thanks for the update, jesh. Also, thanks to MichaelP for the detailed explanation there. Before I mark this as resolved, is there anything else you might need, jesh? If so, just let me know.
Thanks.
05-09-2022 01:20 PM
Hi Jeff.
No thanks. I think I am all good again and MichaelP's reply resolved it.
05-09-2022 02:19 PM
Thanks, jesh. I'll go ahead and mark this as resolved. If you need anything else in the future, please feel free to open up a new thread.
Thanks!