Summary

Question

Customer Environment

Root Cause

Symptoms

Resolution

It is recommended by the installer and Ruckus to connect one of the speakers through the wire and connect the remaining ones wireless if desired.   The following steps and workaround applies to SONOS Standard Setup, which delivery music through standard Wi-Fi networks.

Before you begin, make sure below protocols and ports are allowed.
These are the protocols and ports that SONOS needs to communicate in your network.

Protocols:
-UPnP needs to be on
-Multicast Packets need to be allowed
-BPDU packets need to be allowed
-STP (Spanning Tree Protocol) needs to be allowed
-SONOS units need to be on the same subnet as the controlling device(iPod, computer , etc)
-Wireless client isolation must be turned off if any wireless devices will be controlling SONOS

Below are the ports that Sonos uses:
TCP/IP:
80 (Internet Radio, updates and registration)
443 (Rhapsody, Napster, and SiriusXM)
445 (CIFS)
3400 (incoming UPnP events - Sonos Controller App for Mac or PC)
3401 (Sonos Controller App for iOS)
3500 (Sonos Controller App for Android)
4070 (Spotify incoming events)
4444 (Sonos update process)
UDP:
136-139 (NetBIOS)
1900 (UPnP events and device detection)
1901 (UPnP responses)
2869, 10243, 10280-10284 (Windows Media Player NSS)
6969 (Initial configuration)

Please find more details on: https://www.sonos.com
When you experience troubles in Standard Setup, please go over the recommended steps list for workaround.  

Customer using RUCKUS One, RUCKUS SmartZone, RUCKUS Unleashed 200.14 or older, please follow the below workaround:

When Standard Setup is selected, the WiFi APs will be used to connect speakers to each other.  In this case, it recommended to disabled Directed Multicast/Broadcast:
ruckus(config-wlan)# no qos directed-multicast
ruckus(config-wlan)# qos directed-threshold 0

Customers using RUCKUS Unleashed 200.15 and 200.16 follow the below steps:

In version 200.15 and 200.16, we have implemented the fix by disabling the Directed DHCP. This can be done using the below command.

ruckus(config-wlan) qos directedDHCP disable

Below should be the output on the APs after executing the command:

ruckus(ap-mode)# get qos
Tx Failure Threshold:      50           Dead Station Count: 0

Forward to Querier:        Disabled
Directed DHCP:             Disabled  

Starting from 200.17 version,
We have implemented UI component "SONOS Compatibility" available in the GUI under Wifi Settings >> Summary >> Edit >> Others, which is enabled by default.



With this option, directedDHCP is disabled.
If you disable "SONOS Compatibility" from the GUI, then the "directedDHCP" will be enabled, however, AP will drop the DHCP proxy messages.