Ethernet configuration?

[wolraht]

In my Google Nest Router, when I plug a device into the LAN port, I get no connection to the device.  Tried connecting a PS4 and a Dell Laptop.  In both cases no Ethernet connection was seen.  Is there a setup configuration that needs to take place in the Google Home app to enable the Ethernet connection out of the Nest Router?  The mesh wifi is working fine.

[MichaelP]

Hello @wolraht 

No, there's no configuration required to make the LAN port work. As long as the devices being connected are properly configured to auto-negotiate the Ethernet connection, request an IP address via DHCP, and are connected through a known-good Ethernet cable, they should "just work". I would try a different Ethernet cable to rule that out, but I'd also check the devices to be sure they haven't been configured with static IP addresses from an older network (since Google/Nest WiFi uses a somewhat unusual address range).

[vivlund]

Hello @MichaelP and @wolraht ,

I am having the same problem. I have set my NAS to request an IP address via DHCP, and I can see in the Google Home app that it has been assigned an IP address in the Google Wifi address range. It shows up in Windows Explorer even. When I try to connect to it, I get the error "Device is available but is not responding to connection attempts. A firewall or network security policy on the remote device may be blocking the connection on port "file and print sharing resource." 

If I take the NAS and connect it and my computer to my old router via ethernet cables, I can connect to the NAS and see the settings just fine. Any Ideas?

[MichaelP]

Hello @vivlund 

If it's showing up in the Google Home app with an IP address assigned, then the network can see it, and it can talk to the Google WiFi router. If it shows up in Windows Explorer, then the multicast discovery protocol is working, too. I don't know what's different between the two networks, but at this point, the IP address range is the only thing I can think of. I built my own NAS, so I can't give you any advice on how to investigate this, but I would be digging through the NAS settings to see if there are any places the IP address range is hard-coded. I assume you're rebooting the NAS in between connecting to each network, right?

[vivlund]

Hello @MichaelP, 

I got it to work yesterday by doing the following:

1) made a note of the Google Wifi Router IP address

2) hooked up the Google Wifi router ethernet port to the internet input of the old Linksys router

3) hooked up a desktop computer and the Synology Diskstation NAS to the ethernet ports on the back of the old Linksys router (I did this because the computer had been hard-wired to the old Linksys router, and all the cables were right there.)

4) In this configuration, I used the Synology setup assistant program on the desktop to locate the NAS. (Of course, it was on a separate network created by the Linksys router, but at least I could see the NAS.) It seems during this step, the setup program adds an exception to the NAS firewall for the router. I could not get to this step using the Google Wifi router, as I could see it but could not communicate with it.

5) All the error messages I had been getting indicated a firewall issue, so I logged into the NAS from a browser using the IP from the setup assistant and then used the NAS control panel app to find the NAS firewall.

6) I saw that the NAS firewall had an exception for the Linksys router, so I added an exception for the Google Wifi router's IP address. 

6) Voila, problem solved. I can now use the NAS on the Google Wifi.

Thanks for your help.

[Jeff]

Hey, wolraht.

I just wanted to drop in real fast to see if you were able to get this sorted out or to see if you needed more help on this. Let us know if you're still trying to get things to work.

vivlund, thanks for letting us know what worked for you. That really helps others understand what they need to do as well. I'm happy it worked out.

Thanks.

[wolraht]

Hi Jeff,

I didn't solve why my Nest router would not connect to any devices across the wired ethernet.  I did go buy a new Nest router and set it up as a point and it worked perfectly when I plugged in the same devices that would not work when connected to the first router.  I bought that first router in a set refurbished from Groupon or Woot! or something, so it's entirely possible that it never worked in the first place.  Regardless, I have my setup working now and I'm ok with the configuration.

Thanks!

[Jeff]

Hi, wolraht.

Thanks for coming back and updating us. I'm glad you got everything working for you. As we have our resolution on this, I'm going to go ahead and close up the thread. If you or anybody else needs any more support or has any other questions in the future, please feel free to start up a new discussion.

Thanks.