Skip to main content

Sonos S1 Access to TrueNAS network share

  • January 26, 2026
  • 3 replies
  • 32 views
S

Was having trouble giving Sonos S1 access to my iTunes library hosted on TrueNAS Community Edition 25.10.1 (Goldeye) and figured it out with information from this forum and the TrueNAS forum, so posting this to help others that are also struggling.

Step 1: Configure the SMB service in TrueNAS to “Enable SMB1 support” and “NTLMv1 Auth”. Security folks will tell you this is insecure, and it is in 2026. Anyhow, let’s continue.

Step 2: Create your SMB share in TrueNAS and give it proper permissions (not documented here. If you are using TrueNAS you probably know how to do this already)

Step 3: In the SONOS app, add the TrueNAS network share to your music library.

Step 4: Wait for music to sync

Step 5: Try to play music from your library. You should be able to browse your collection, but when you go to play a file, it will fail with “Unable to play <song file>, access to <network share> denied”

Step 6: Go to your shell in TrueNAS and run:
cli
service smb update smb_options="unix extensions = no"

Step 7: Try to play music from your library again, it should work now.

    3 replies

    Stanley_4
    • Stanley_4
    • Lead Maestro
    • January 26, 2026

    SMB v1 is insecure and all hardware that is capable of running v2 or newer should.

    Sonos S2 uses the newer SMB code but the S1 only hardware lacks the ineternal memory to support the newer v2 code.

    So the choice is simple, allow v1 or have no access, as there is no way to add memory to 20 year old Sonos gear to host v2 code.

    If running v1 it does make sense to restrict it to just the music files and to set it as read-only to reduce the risk.

    An excellent security measure is to run an SMB v1 proxy on a well locked down device that uses a more secure protocol to apllow read-only access the actual files on your NAS. In my case I used NFS to connect to my NAS that didn't allow any SMB access.

      S
      • sonoswes
      • Author
      • Contributor II
      • January 27, 2026

      SMB v1 is insecure and all hardware that is capable of running v2 or newer should.

      Sonos S2 uses the newer SMB code but the S1 only hardware lacks the ineternal memory to support the newer v2 code.

      So the choice is simple, allow v1 or have no access, as there is no way to add memory to 20 year old Sonos gear to host v2 code.

      If running v1 it does make sense to restrict it to just the music files and to set it as read-only to reduce the risk.

      An excellent security measure is to run an SMB v1 proxy on a well locked down device that uses a more secure protocol to apllow read-only access the actual files on your NAS. In my case I used NFS to connect to my NAS that didn't allow any SMB access.

      Unfortunately with TrueNAS, there is only a single instance of the SMB service so turning on v1 turns it on for all the shares.

      That being said… what a great idea you have, using another device running SMBv1 as proxy to TrueNAS. I’ve got an extra Raspberry Pi that might just work for this.

      Stanley_4
      • Stanley_4
      • Lead Maestro
      • January 27, 2026

      I made some notes on my Live Journal account, a Pi Zero has more than enough power to serve multiple streams..

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

       

      Terms & ConditionsCookie settingsAccessibility statement