Skip to main content
Question

Cannot get speakers working consistently and reliably on Google Wifi Pro network

  • July 14, 2024
  • 2 replies
  • 86 views
W

We are on a new Google Wifi Pro network and have nine speakers and nearly nothing is working and it is certainly not working consistently. We've had this network for a couple weeks and everything was working but everyday it is a little different in terms of what works and how. I have to believe there must be some setting(s) in the Wifi that could be the problem but we're running a stock, unmodified, default settings configuration. Sometimes the speakers will work from Spotify running on a PC, sometimes speakers don't show up, sometimes groups don't show up, sometimes it works and then stops working. We are running a bed and breakfast and have invested thousands in these speakers and they are slowing driving me insane. I've also invested in Sonos Pro thinking maybe that would be the difference.

 

Is there a special configuration for Sonos or the Google network I should be using?

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

2 replies

Bumper
  • Bumper
  • July 14, 2024

Here’s info on using mesh systems with Sonos, scroll down for the mesh info. 
 

 

You need to put it in bridge mode, this link is for Nest Wifi but prob similar or will give you an idea of what to look for  

https://support.google.com/googlenest/answer/6240987?visit_id=638565561801237089-1844361076&rd=1

W
  • whitedoeinn
  • Author
  • Contributor I
  • July 14, 2024

In my case I have a Spectrum cable modem connected physically to my first Nest Pro router and I have three Nest Pro APs, one on each floor of our bed and breakfast. Sonos tech support says I have double NAT, which is the problem but Spectrum support says their modems are not doing NAT and that they are not configurable in any case. I’ve looked into how to detect double NAT and seems if I see two private addresses in a traceroute that is the litmus test, I’m not seeing that.

 

C:\Users\bebew>tracert www.google.com

Tracing route to www.google.com [172.253.124.104]
over a maximum of 30 hops:

  1     4 ms     2 ms     3 ms  192.168.86.1
  2    19 ms    24 ms    12 ms  syn-024-181-244-001.res.spectrum.com [24.181.244.1]
  3    13 ms    14 ms    11 ms  lag-161.dtr01mantnc.netops.charter.com [159.111.162.18]
  4    26 ms    37 ms    29 ms  lag-14.crr01hlrgnc.netops.charter.com [96.34.65.132]
  5    39 ms    34 ms    40 ms  lag-404.crr02spbgsc.netops.charter.com [96.34.95.68]
  6   157 ms    39 ms    32 ms  lag-808.bbr01spbgsc.netops.charter.com [96.34.2.50]
  7    42 ms    42 ms    44 ms  lag-804.bbr01atlnga.netops.charter.com [96.34.0.184]
  8    44 ms    42 ms    49 ms  lag-801.prr01atlnga.netops.charter.com [96.34.3.35]
  9    45 ms    45 ms    43 ms  con01stlsmo.stls.mo.charter.com [68.112.12.13]
 10    67 ms    53 ms    45 ms  172.253.71.213
 11    95 ms   124 ms    49 ms  108.170.248.104
 12    50 ms    64 ms    96 ms  142.251.51.101
 13    39 ms    39 ms    40 ms  142.251.51.106
 14    52 ms    74 ms    65 ms  108.170.236.163
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21    44 ms    44 ms    40 ms  ys-in-f104.1e100.net [172.253.124.104]

According to Google’s online help (linked from your response, thank you BTW), I cannot disable NAT on my primary Nest router without loosing the APs, so I feel like I’m between a rock and a hard place.

Terms & ConditionsCookie settingsAccessibility statement