12-22-2023 05:42 AM
I have a Gen1 Google Wifi mesh (3 units). It has generally worked well. I run a SMB server on a Raspberry Pi hardwired to a mesh unit. It serves music to a collection of SONOS units (connected via WiFi).
The problem I am having is that when the Pi is connected to a non-principal mesh unit, it can sometimes take upwards of 45 seconds to successfully start supplying music via SMB. The SONOS times out, of course. But eventually the SMB connection succeeds and all is well. It stays this way at least for the course of a music session.
I can reproduce this behavior when connecting to the Pi using SMB on my Windows PC, but the delay is shorter.
Connecting to the Pi using HTTP or SSH from my computer (on wifi) never fails.
Here's the kicker. If I move the Pi to the primary mesh unit (which is logically closer to the SONOS boxes), it never fails in this way.
Any ideas about what's happening. (I may have to buy a USB Ethernet adapter so I can snoop the Ethernet at the Pi. Have not done so yet.)
01-31-2024 05:05 PM
Hi TedWobber,
That certainly isn’t the experience we want you to have, and we apologize for the delay. A few questions: are you using a modem/router combo from your Internet service provider (ISP)? Which Google/Nest router are we working with? What device are you using to set up your network (iOS or Android)? Do you have the Internet on your modem?
It sounds like you're facing an interesting connectivity issue with your Google Wifi mesh system and your Raspberry Pi-based SMB server. While relocating the Pi to the primary mesh unit solves the problem, understanding the cause can help prevent future issues or optimize your setup further. Here are some potential explanations and steps you can take:
Possible Causes:
Troubleshooting Steps:
Additional Tips:
By trying these steps and considering the potential causes, you should be able to identify the reason behind the SMB connection delays and optimize your network setup for a smoother experience. If you need further assistance, don't hesitate to provide more details about your network configuration and any additional troubleshooting attempts you've made.
Best,
Dan