Skip to main content
Trending Lyricist I
January 27, 2022

Sonos making thousands of SMB3 connections to Synology

  • January 27, 2022
  • 66 replies
  • 3055 views

Not sure if anyone else is experiencing issues with Sonos Music Library and the Synology NAS becoming unresponsive or very sluggish, or with random speakers disappearing from the S2 app.

 

I recently enabled the Music Library feature in Sonos (before the 13.4.1 update in Dec 2021 which introduced SMB3 support). At that time, I configured my Synology NAS to use SMB1 to allow the connection to work. I was on DSM Version: 7.0.1-42218 and running S2 13.3.2. Somewhere around 11/25/21, my Synology started going offline and become unresponsive. I was running a DS1517+ with 2GB of RAM and noticed that the SMB process was eating a lot more RAM than usual. Also, started seeing thousands of connections from the Sonos speakers, multiple times for each speaker. My Sonos updated to 13.4, but the issue still remained.

I opened a case with Synology and they determined that the Sonos speakers were opening hundreds of connections per speaker and leaving the connections open. This was slowly draining the memory until the NAS would become unresponsive.

On 12/7/21, S2 updated to 13.4.1 which introduced the SMB3 support. I turned off SMB1 on the Synology NAS and still saw the hundreds and thousands of connections. I would also see the speakers attempt an SMB1 connection still which was denied by the speakers. For testing, we tried leaving SMB1 on, but still saw the large amount of connections from the Sonos speakers.

I ended up switching to a newer DS1621+ with 8GB of RAM and the issue still continued to happen, but took several days instead of just one. At one point, the number of active connections from Sonos was near 4000.

 

After switching to the DS1621+ with more memory, the issues started getting worse on the Sonos side. Several speakers would start to show up as ZP100 (would be various speakers and not always the same ones). This marked these speakers as incompatible with the S2 app and so I couldn’t do anything relating to the music library (like remove it) until the affected speakers were rebooted. If you tried going to http://<ip of speaker>:1400/xml/device_information.xml nothing would show up, or just the XML banner stating “This XML file does not appear to have any style information associated with it. The document tree is shown below.” The speakers were acting similar to the old NAS where they would start to become unresponsive. I can only guess that with the hundreds of open connections to the NAS, the memory utilization would get very high and the speaker would stop responding correctly.

 

After rebooting the speaker that showed up as a ZP100 you could then hit the XML page and the speaker showed up correctly as a Sonos One. I would also get some speakers that would just completely drop from the application, but after a reboot, they’d show up just fine.. In all cases, my wireless controller showed all speakers connected on the network and they all responded to pings. After a reboot of all the speakers, they all showed up correctly in the S2 app and could all play music from the Synology. Also, after a reboot of the speaker, all the connections would slowly drop on the NAS and memory usage would return to normal.
 

The whole system would run fine for a couple of days and then the connections would start appearing on the NAS at various times (not just at the 2am re-indexing time). I also noticed that whenever I had the S2 app up and when I would explore a Sonos playlist that contained music from the NAS, I would get SMB1 failures in the NAS logs for the associated speaker. I believe that the code is still set to use SMB1 for some functions and is getting blocked by the NAS..

 

If I disable the Music Library, all the speakers stay connected to the wifi network and I can stream music with no issues for several days. The memory on the NAS remains at normal levels and doesn’t climb over time. I still see SMB1 connections whenever I pull up the S2 app as long as the Sonos playlists exist that point to music on the NAS, even if the Muisc Library is disabled. I still think the Sonos code is trying to use SMB1 to update something either with album art or the track icons and is having trouble. If I browse to the album directly under Music Library, the album art does show correctly. It just seems to be the track icons in the playlist has trouble populating. These playlists were created by selecting various tracks in the Music Library and adding them to the Sonos playlist.

 

I have tickets open with both Synology and Sonos and currently waiting to hear back from Sonos after giving them countless diagnostics and logs. It seems that the diagnostic logs don’t show the connections to the NAS and so support doesn’t have any visibility into the problem other than looking at the thousands of connections in the Synology logs that I’m providing them.

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.

66 replies

ChewbuckaAuthor
Trending Lyricist I
February 26, 2022

Definitely not fixed in 14.2.

I think I’ve been lucky so far and haven't seen the hundreds of connections yet.

I still see random SMB1 connections to the NAS and will need to keep pushing support to find out why that is doing that.

Also, if you remove the music library, no connections should be made to the NAS. I’m still seeing the speakers making connections which means that the software is saving the username and password even though you are deleting the service that was using it. This needs to be fixed as well. If you delete the music library which contains the username and password to connect to the share, those credentials should no longer be available and so the speakers should not be able to successfully connect to the NAS.

Trending Lyricist I
February 26, 2022

root@ix4-300d:/opt# smbstatus | grep Music | grep Fri
Music        2043    192.168.1.113 Fri Feb 25 05:46:00 PM 2022 EST  -            -
Music        1316    192.168.1.113 Fri Feb 25 05:37:49 PM 2022 EST  -            -
Music        9053    192.168.1.113 Fri Feb 25 07:12:24 PM 2022 EST  -            -
Music        8574    192.168.1.113 Fri Feb 25 07:07:14 PM 2022 EST  -            -
Music        9014    192.168.1.113 Fri Feb 25 07:12:16 PM 2022 EST  -            -
Music        1307    192.168.1.113 Fri Feb 25 05:37:47 PM 2022 EST  -            -
Music        2010    192.168.1.113 Fri Feb 25 05:45:53 PM 2022 EST  -            -
Music        9064    192.168.1.113 Fri Feb 25 07:12:26 PM 2022 EST  -            -
Music        1287    192.168.1.113 Fri Feb 25 05:37:43 PM 2022 EST  -            -
Music        2012    192.168.1.113 Fri Feb 25 05:45:54 PM 2022 EST  -            -
Music        9051    192.168.1.113 Fri Feb 25 07:12:24 PM 2022 EST  -            -
Music        1312    192.168.1.113 Fri Feb 25 05:37:48 PM 2022 EST  -            -
Music        9049    192.168.1.113 Fri Feb 25 07:12:23 PM 2022 EST  -            -
Music        9055    192.168.1.113 Fri Feb 25 07:12:25 PM 2022 EST  -            -
Music        1318    192.168.1.113 Fri Feb 25 05:37:49 PM 2022 EST  -            -
Music        1314    192.168.1.113 Fri Feb 25 05:37:48 PM 2022 EST  -            -
Music        9047    192.168.1.113 Fri Feb 25 07:12:23 PM 2022 EST  -            -
Music        2005    192.168.1.113 Fri Feb 25 05:45:51 PM 2022 EST  -            -
Music        1282    192.168.1.113 Fri Feb 25 05:37:42 PM 2022 EST  -            -
Music        2039    192.168.1.113 Fri Feb 25 05:45:58 PM 2022 EST  -            -
Music        9028    192.168.1.113 Fri Feb 25 07:12:20 PM 2022 EST  -            -
Music        2041    192.168.1.113 Fri Feb 25 05:45:59 PM 2022 EST  -            -
Music        1305    192.168.1.113 Fri Feb 25 05:37:46 PM 2022 EST  -            -
Music        1303    192.168.1.113 Fri Feb 25 05:37:46 PM 2022 EST  -            -
Music        2037    192.168.1.113 Fri Feb 25 05:45:57 PM 2022 EST  -            -

 

So what happens is during a “session” the controller opens the connections. Then if you don’t use the Sonos, or go back later and change something, it opens an entire new set of connections. I’ve only ever seen SMB3_02 protocol used by the Sonos but I’m not looking very carefully. At least the orphaned connections are 3.02.  I have 75 from Thursday just sitting there doing nothing. The idea of clearing the music library is interesting, but I loath doing that because with this new bug I’ve had scan failures so I risk losing everything (I have 20000 songs on the nas).

 

 

ChewbuckaAuthor
Trending Lyricist I
February 26, 2022

I just re-added my music library and I can see the associated product making thousands of connections to the NAS. On the bright side, there’s only one active connection that is showing, so the speaker appears to be opening and closing the SMB3 connection for every song on the NAS, but so far they aren’t staying open. Not sure why the speaker has to keep closing and opening new connections. I’ll keep an eye on it and see if they start to stay open.

Trending Lyricist I
February 27, 2022

In my case I have a theory that it may be two controllers creating connections back and forth, when played together. I have two stereo pairs in each room, but I usually play the rooms together.  When I see large numbers of connections I see both controllers from my two stereo pairs. But when things are well behaved I see only one ip sharing 5 connections. Also when it works properly with a single ip the album art is much quicker to load and I don’t get blanks when I scroll through the queue. If your system has two or more pairs that are linked to play together, this could be the root cause.

 

ChewbuckaAuthor
Trending Lyricist I
February 28, 2022

In my case I don’t have any stereo pairs, but now I’m seeing the SMB connections staying open again. Currently up to 238 connections since yesterday. If I don’t remove the NAS from the music library, this will continue to grow until the speakers stop responding on the network. Support tries to blame the wi-fi for this behavior, but it’s the number of open connections to the NAS that is consuming onboard RAM of the speaker and this causes the speaker software to stop responding. The high number of connections to the NAS is the first symptom. The second is when the http://<ip of speaker>:1400/xml/device_description.xml page stops responding. My home automation system uses these pages to query the speakers for services and I typically see the speakers drop offline just before they start crashing. The third symptom is that the speakers will either show up as ZP100 speakers and are marked incompatible, or they simply stop showing up in the mobile app.

ChewbuckaAuthor
Trending Lyricist I
February 28, 2022

Definitely not fixed in 14.2.

I think I’ve been lucky so far and haven't seen the hundreds of connections yet.

I still see random SMB1 connections to the NAS and will need to keep pushing support to find out why that is doing that.

Also, if you remove the music library, no connections should be made to the NAS. I’m still seeing the speakers making connections which means that the software is saving the username and password even though you are deleting the service that was using it. This needs to be fixed as well. If you delete the music library which contains the username and password to connect to the share, those credentials should no longer be available and so the speakers should not be able to successfully connect to the NAS.

Confirmed that it’s not fixed in 14.2. I’ve reached out to support again to find out if it was supposed to be fixed. I also let them know about the continued SMB1 connections being attempted.

Trending Lyricist I
February 28, 2022

I noticed my speakers, which are all wifi connected have deauths in the router log. This causes another Zone player to take over the connections and the old ones are abandoned. Something may have changed recently where they are more likely to disconnect from the wifi network. If you have another AP, or instability in your wifi , that could be a cause. In my case it just started happening with the December update, and none of my other wifi devices are deauthing, so the problem seems specific to Sonos.

If the smbstatus shows multiple ips rather than a single ip, that is also a symptom of this same problem.

ChewbuckaAuthor
Trending Lyricist I
March 9, 2022

I haven’t noticed an issue with the speakers de-authing on the wifi so far. The only thing is the hundreds of connections, the SMB1 connections, and the continued connections to the NAS even after removing the music library which has the saved credentials. This should be a security concern since the credentials should not be able to be used once the connection to the music library is removed. I haven’t removed my playlist, that contains songs from the NAS, until they can get this fixed.

ChewbuckaAuthor
Trending Lyricist I
March 27, 2022

Just as an FYI, at the direction of support, I removed all songs in the playlists and I no longer saw any connections from the speakers as expected.

I’ve installed version 14.4 and have re-enabled the Music Library. I’ll keep an eye on the connections to the NAS to see if the issue remains with the hundreds of connections and SMB1 attempted connections.

James L.
Retired Community Staff
March 28, 2022

Hi folks,

 

I’m happy to say that this issue has been resolved with the latest S2 update (14.4). Sonos players should no longer be sending excessive requests to your NAS drives when using the music library when updated to this version.

Please let our customer care team know if you’re still experiencing this issue after updating all players and controllers to 14.4. 🙂

Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.