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. 

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. 

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 ;)

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 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.

So I found the older logs and it appears to be more than just the Play:1 speakers. Also have logs showing a Sonos Arc, Playbar, and two Play:1 speakers (matched via IP address) with failed logins via SMBv1 starting on April 13.

I have not however figured out a way to replicate the issue. Continuing to try different things and will comment back if I discover a repeatable method.

Hi @fache 

Thanks for the additional info.

Thank you for the detailed response!

I am running an Orbi mesh network and all Sonos speakers are wireless, but the NAS is wired into a hub which is wired back to the main Orbi router. We do have multiple satellites due to the layout and building materials of the house (wireless does not seem to like terracotta tile), plus an additional need to act as bridges in some cases for wired devices in specific areas.

I thought I had disabled any/all guest access to the NAS, but given the logs it appears something is getting through. I found an additional setting in advanced network options that seems to restrict guests/anonymous users from viewing shared folders via SMB and will see if this reduces the flags in the logs. It was set to Disabled, but I have it now set to Enabled (strict).

I set up the music library using the Windows desktop version of the Sonos app and configured to direct network share locations, not mapped locations/drives, which prompts for user credentials to complete.

I guess the one lasting facet is wondering why Sonos is seemingly attempting to access the NAS as a guest/anonymous first when it does have proper credentials configured, but perhaps this particular SMB setting will prevent it.

Upon further searching, it does seem that QNAP has many inquiries as to why a guest account exists and whether it can be truly disabled. While it is not configured or activated as a User account via NAS UI, I found guest in the /etc/passwd file on the NAS, but on a positive note, the guest account is not accessible via SSH.

Thank you all again for the support!

Just FYI,

Happened again today after making the SMB change (seems to have had no effect), this time from my Playbar that is sitting on the same shelf open air 2 feet from an Orbi Satellite, one that is actually wired back to the Orbi Router. One difference is that this time I had linked the Playbar to a Sonos Move speaker and noticed that I was able to queue up a song with my iPhone Sonos S2 app, it started, then stopped playing and showed an error accessing the music file, had to press Play again on the app, and it started and stopped again with another access error, then pressed Play on the app and it continued with no further issue, which seems to align with the following log warnings.

Hi @fache 

You are unable to change the SonosNet channel because SonosNet is not in use. It also therefore does not interfere with your WiFi, so is nothing to worry about.

In addition, only your Arc and Playbars are using channel 11 - the rest are on 5GHz (channel 48 at the time of the diagnostics).

You could, of course, try SonosNet by connecting one (not an Era) device to ethernet, though I would recommend changing the SonosNet channel straight afterwards (once a couple of minutes have passed and all rooms show in the app). If this makes any rooms disappear, go back to channel 11 to pick them up again and try once more.

I hope this helps.