01-21-2024 09:06 AM
I have the Google AC-1304 nest wifi setup in my home (3 devices). I have all computers, smartphones, TVs, Sonos speakers, security system, etc all connected to this wifi. I do not have a double NAT situation; nothing is connected to my ISP's wifi or hardwired to the router. As a result, everything in my house is assigned a private IP address by the Google nest within the 192.168.86.20 to 250 range of IP addresses. I have no port forwarding or DHCP IP reservations.
In general, I've had very few issues setting up what I need without connectivity issues.
However, I've recently set up a Ubuntu server as an in-house media server using Emby. I haven't been able to get my smartTV (using an Emby app) or a Windows 11 PC to access the Emby server. In diagnosing the situation, I decided to make it simple and avoid any setup issues with Emby; I also set up a simple HTTP server on the Ubuntu device that serves up a simple "Hello World" html page. When I access http://localhost or http://192.168.86.34 on that computer, it works fine. However, when I use any other device to attempt to access this computer via the private IP, the connection times out. I've made sure the firewall config on the ubuntu server is set to allow port 80. Another footnote: the Ubuntu server doesn't have a wifi card, so its LAN is connected directly into the AC-1304, and I've verified with Google Home app that all devices I've been testing with (Windows 11, android, and LG TV with WebOS) are all on the same LAN.
I've attempted to factor out dependencies on any OS: I've attempted both ping and http to the Ubuntu device from Windows 11, the TV's browser app (in WebOS), and Android. All timeout. I've also attempted to set up file sharing within my LAN between two Windows 11 devices with no luck. In short, even though all other devices are working as they should (ie, no issue playing Spotify from my PC or my Android to the Sonos wireless speakers; all connected on my Google nest), I've hit a dead end in trying to determine what in this Google nest config is preventing (a) having one device be a simple HTTP server and accessible from other devices on the LAN, (b) two devices (Windows 11 to Ubuntu or Ubuntu to Windows 11) pinging the other, or (c) two Windows 11 PC's from sharing a hard drive. I've tried to factor out OS and firewall dependencies.
My next move will be to take the Google nest network out of the equation, and move the Ubuntu server and the Windows 11 PC to be hardwired connected into the ISP router, on that LAN, and verify that the PC can access the Ubuntu server independent of the Google nest LAN. But, I thought I'd see if there were any suggestions on settings within the Google nest setup that I should further diagnose because ultimately I need this setup on the google nest LAN. Thanks for any help.