Skip to main content
Question

Music Files on NAS, SMB 2 or 3 -- Samba in Container?

  • August 23, 2020
  • 4 replies
  • 825 views
R
Forum|alt.badge.img
  • Ramias
  • Contributor III
  • 5 replies

Don’t want to run SMB 1 on my NAS.  Have 3 older Play 5’s so am on S1 and my workstations are all Macs so no Sonos-native HTTP sharing.

Thinking of running NAS at SMB 2.1 (I think that is required for Time Machine; will test with 3.0 only and see) which if course breaks access to Sonos for my music files on the NAS.

Has anybody run a Docker container of Samba on the NAS (with its own IP address) and mounting your audio files and allowing that container to share out your audio files via a separate IP as SMB 1.0?

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.

4 replies

Stanley_4
  • Stanley_4
  • Lead Maestro
  • 12319 replies
  • August 23, 2020

I used both of the methods here with a Raspberry Pi, the SMB v1 gateway is pretty slick and doesn’t require any extra storage. A Pi Zero-W is more than good enough for this.

https://stan-miller.livejournal.com/

R
Forum|alt.badge.img
  • Ramias
  • Author
  • Contributor III
  • 5 replies
  • August 23, 2020

This is what I did as a script on my QNap:

 

docker container stop sonossamba
docker container rm sonossamba
docker image rm dperson/samba
docker run -d \
	--init \
	-p 139:139 \
	-p 445:445 \
	-e USERID=1006 \
	-e GROUPID=100 \
	-e GLOBAL="ntlm auth = ntlmv1-permitted" \
	-e SMB=1 \
	-e USER="sonos;sonos" \
	-e SHARE="music;/Music;yes;yes;no;sonos" \
	-e TZ=EST5EDT \
	-e SHARE2="audiobooks;/Audiobooks;yes;yes;no;sonos" \
	-e RECYCLE \
	--network=qnet-static-bond0-0fa2ce \
	--ip=192.168.0.253 \
	--mac-address=02:42:00:00:02:53 \
	--restart=always \
	-v /share/Music:/Music \
	-v "/share/Audio Books":/Audiobooks \
	--name sonossamba \
	dperson/samba:latest

 

T
  • Thomas M C
  • 10 replies
  • October 16, 2020

As of samba 4.11 it does not support smb1 by default. Se release-notes.
 

However it is still possible to force-anable SMB1. But it is unsupported, and will be removed at some point.

I had to put this in my samba412, to get Sonos to connect:

# for Sonos:
ntlm auth = yes
server min protocol = LANMAN1

But be warned, at some point support for SMB1 will be removed in samba (see release-notes for details).

In this forum I will point out this passage:

As Microsoft no longer installs SMB1 support in recent releases
or uninstalls it after 30 days without usage, the Samba Team
tries to get remove the SMB1 usage as much as possible.

Maybe Sonos should upgrade from SMB1 by now, or some major functionality will be gone (playing music from MS windows-computers).
 

Br

Thomas

Stanley_4
  • Stanley_4
  • Lead Maestro
  • 12319 replies
  • October 16, 2020

From the release notes above, this is going to be a problem for Legacy Sonos gear:

SMB1 is officially deprecated and might be removed step by step
in the following years. If you have a strong requirement for SMB1
(except for supporting old Linux Kernels), please file a bug
at https://bugzilla.samba.org and let us know about the details.

 

My solution is going to be a Raspberry Pi running an obsolete OS and the last SMB v1 supporting Samba version that I can find. I’ll keep two Pi handy, a SMB v1 file server and an SMB v1 to NAS gateway.

Terms & ConditionsCookie settingsAccessibility statement