Play:1 speakers still seem to be using SMBv1 on S2

Might be helpful if you were to include a diagnostic, so the forum moderators have hard data to look at. Or call Sonos Support directly, which would likely be faster than waiting for a forum moderator to have time to look at the situation. 

And no, there’s no ‘setting’ in the controller to force a particular version of SMB, but I would be very tempted to force a reload of the OS on those particular speakers by unplugging them from power for at least a minute. It does seem odd that they’re trying to connect with SMB v1, when you get an answer, would love it if you were to post an update here. 

I have recently unplugged both speakers as I replaced them in my surround setup (Arc+Sub) with new Era100s and moved the Play:1 speakers, one to each of my kids’ rooms, so they were powered off for 15+ minutes each.

I submitted diagnostics through the Sonos app and will reach out to support directly in the meantime.

Thank you for the reply!

Always worth making the suggestion, when it’s not clear one way or the other.  ;)

Make sure you call in with that diagnostic number,  they don’t look at random diagnostic submissions. 

Interestingly enough, I just got off the phone with Sonos Support who informed me that all Sonos speakers only use SMBv1. I’m fairly certain that is not true since I have multiple generations of Sonos speakers, but not all of them are experiencing this issue. Kinda disappointing from support.

Also:https://support.sonos.com/en-us/article/release-notes-for-sonos-s2?language=en_US

13.4.1

Release date: 12/07/2021

Sonos products can now connect to local music library shares using SMBv2 and SMBv3.

Agreed, sounds like the rep was either misunderstanding, or misinformed. S1 uses only SMB and NTML v1, but S2 uses SMB v2 or v3. I’ve blocked SMB v1 on my WD NAS, but have never looked to see if there were connection attempts from the Sonos. 95% of what I listen to is from that NAS, and it’s been working fine since S2 came out. 

Post that diagnostic number here. The forum moderators have support experience, I think, and while are often busy with moderation duties, might be able to take a look, since they have the ‘magic Sonos access’ to the diagnostics. 

I’m still wary about this being a Sonos issue, though. It seems odd to me (with no special knowledge) that Sonos is even attempting to reach out with SMB v1 using the S2 client. But, I’m not looking at what you are, either.
 

Please, keep us posted here ;)

I found that I could flip my SYNOLOGY NAS between SMBv1 and SMBv2 while music was playing. without any issues.

The diagnostic number is 871851211. Thanks again for the input and suggestions. I’m pretty sure a recent NAS (qnap) upgrade disabled SMBv1 and then I started seeing the access issues in the server log tied to IP addresses that I was able to trace back to the Play:1 speakers.

The latest two attempts were this morning around 5:47:16am. Also to note, whether relevant, is that I have an alarm set to go off at 5:45am that plays a random song from a set playlist. So 2 minutes and 16 seconds after the alarm starts playing the first song, there is an SMBv1 access violation, maybe trying to look up the next song?

Thanks again!

Hi @fache 

Welcome to the Sonos Community!

Could you please post a screenshot of your NAS drive’s settings page? Specifically, the one referencing SMB options? Please also include the page that shows which software version your NAS is using. Thank you.

Hi and thank you!

Attached snapshots of NAS Firmware version, log, and SMB configuration. To note, there have not been any additional instances since. There were a couple instances prior, but did not save those logs.

Hi @fache 

Thanks for supplying those - I’ve passed them on to the engineer that requested them.

You don’t see this error anymore? As in, it’s not 100% reproducible? If so, this will be helpful to know, so please clarify, if you don’t mind. Thanks.