Hi @music1980 

Welcome to the Sonos Community!

First, please confirm that 192.168.1.218 is indeed the IP address of your server.

Next, I recommend ensuring that the minimum level of SMB set to be used is SMBv2 - this can be done by editing the /etc/samba/smb.conf file to include the following line under the >global] section:

min protocol = SMB2

Restart the Samba server after making changes.

If you still encounter issues, please submit a support diagnostic and reply here with the number given. Thanks.

I hope this helps.

Dear Colin,

thank you for your reply.

I have done as you suggested. I tried to add min protocol = SMB2 under rGlobal] section without lucky.

I apologize but I believe that I miss some informations with my previously post.

I’m try to perform a sharing point (by SMB) of a rclone mounted Gdrive.

Maybe I should have written a better title like “access to rclone mount via samba on Rpi ubuntu server”.

As described before I can connect to this shared point from my MacOS, Win, and Android, but I have no lucky from Sonos. Rclone mounted point shared via SMB works fine, I can read and write from MacOS, Win.

To test SMB I also created a shared point of a folder placed under home (under linux server) and Sonos can connect to without problem.

Anyway I send a diagnostic report with number 1251667669.

Sincerely

Hi @music1980 

I am, at best, an amateur user of Linux, but as far as I understand it, the SMB protocol is all Sonos will care about - the fact that there’s an rclone mount involved shouldn’t matter, as by that point, it should be transparent to the client. However, not only could I be completely wrong about this (we have no internal reference material for Linux because we just don’t support it), but the fact that you can get a local folder on the server shared with Sonos to work correctly, I would have to say that the evidence is fairly damning that rclone is the problem. The diagnostics indicate error 95, which is “Operation Not Supported” - this usually occurs as a reaction to the SMB version in use, but I suppose rclone might be inducing it.

You may have success by ensuring that Sonos/Samba has the right permissions to view the rclone mount, but as other clients can connect to it without issue, I kind of doubt that this is the answer.

I did check my own smb.conf file again and realised I forgot that I had changed part of it (due to the thread you linked to above). The relevant parts now read:

client min protocol = NT1

client max protocol = SMB3

server max protocol = SMB3

server min protocol = NT1

unix extensions = no

follow symlinks = yes

ntlm auth = yes

These settings work with my S2 system, but also allow SMBv1 access from some Android apps I use. Please try removing the min protocol and max protocol lines in your current smb.conf file and replace them with the server/client lines shown above, as well as adding/changing the other lines. Be sure to keep a backup of your original smb.conf file somewhere in case you need to revert. If this does not work, I recommend disabling SMBv1 on your server to maximise security.

With a bit of luck, you’ll get a response from someone who knows a lot more about this than I do.

I hope this helps.

I haven’t tried sharing anything using my Pi other than from a local non-SMB v1 NAS but that worked quite well.

I’ll link to my very old instructions, maybe you can see something different there.

SMB v1 Gateway  or  https://stan-miller.livejournal.com/357.html

Hi @Corry P ,

I tried to add/remove those relevant part as you suggest without lucky.

To create a Gdrive a mount point with rclone I followed this guide https://medium.com/@artur.klauser/mounting-google-drive-on-raspberry-pi-dd15193d8138

@Stanley_4 thank you for your suggestion. I tried to add also 

create mask = 0555
directory mask = 0555

under my sharing point in smb.conf. But nope.

Anyway it is strange because from all my other device I can reach the sharing point without problem.

This is my smb.conf file

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 

#======================= Global Settings =======================

>global]
client min protocol = NT1
client max protocol = SMB3
server max protocol = smb3
server min protocol = NT1
unix extensions = no
follow symlinks = yes
ntlm auth = yes



## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic backup domain controller'
# or 'domain logons' is set 
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a iprofiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the inetlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
#   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

>printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
sprint$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin


>sambashare]
    comment = Samba on Ubuntu
    path = /home/ubuntu/mnt/gdrive/multimedia/
    read only = no
    browsable = yes
    write list = ubuntu
    valid users = ubuntu
    create mask = 0555
    directory mask = 0555

>sonos]
    comment = Samba on Ubuntu
    path = /home/ubuntu/sonos/
    read only = no
    browsable = yes
    write list = ubuntu
    valid users = ubuntu

Hi @music1980 

Shouldn’t that last line read valid users = sonos?

Assuming Sonos is signing in to an account called sonos, of course, and that /home/ubuntu/sonos is a symbolic link to the gdrive mount. You’d also need to make sure that sonos is part of the samba user group.

If Sonos is signing into the sambashare account, however, then I think you’d want valid users = sambashare and write list = sambashare (for general use, not Sonos’) under the dsambashare] section.

Please take all this with a pinch of salt - I’m going by my own sense of logic rather than by any actual knowledge.

I hope this helps.