# Only bind to the named interfaces and/or networks you must use the # This can be either the interface name or an IP address/netmask # The specific set of interfaces / networks to bind to Server string = %h server (Samba, Ubuntu) # server string is the equivalent of the NT Description field # Change this to the workgroup/NT-domain name your Samba server will part of # "testparm" to check that you have not made any basic syntactic # NOTE: Whenever you modify this file you should run the command # behaviour of Samba but the option is considered important # - When commented with "#", the proposed setting is the default # differs from the default Samba behaviour # - When such options are commented with " ", the proposed setting # Some options that are often worth tuning have been included as Samba has a huge number of configurable options most of which # smb.conf(5) manual page in order to understand the options listed # This is the main Samba configuration file. # Sample configuration file for the Samba suite for Debian GNU/Linux. But nope.Īnyway it is strange because from all my other device I can reach the sharing point without problem. To create a Gdrive a mount point with rclone I followed this guide you for your suggestion. I tried to add/remove those relevant part as you suggest without lucky. With a bit of luck, you’ll get a response from someone who knows a lot more about this than I do. If this does not work, I recommend disabling SMBv1 on your server to maximise security. Be sure to keep a backup of your original smb.conf file somewhere in case you need to revert. 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. These settings work with my S2 system, but also allow SMBv1 access from some Android apps I use. 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). 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. 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. 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. If the they are available to android but not windows, it would indicate that samba is working correctly but there is a window compatibly issue that the above solution should resolve.Hi 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. I also suggest and easy test to see if your samba shares are actually available on the network is to check with a file manager app the supports network locations from an android phone. If you feel you really need firewall enabled (ie not already behind router firewall) there is a guide to setting firewall for WSDD here at step 11. It worked for me out of the box with the standard smb.conf after disabling firewall. The only solution that worked for me was fairly simple, it was to install WSDD to enable Windows web services discovery, guide and explanation here: WSDD set up guide. While adding server min protocol = NT1 to smb.conf and/or enabling SMBv1 on windows has worked for some it did not solve the issue for me. I had this issue after fresh install of 20.04, even my old smb.conf from 18.04 which had worked, would not allow windows(10) to see the samba shares. For example: sudo mount -t cifs //server-name.local/share-name /mountpoint -o guest,uid=1000Īfter some syntax changes you can set this up as a systemd automount in fstab so the user doesn't have to use the terminal.įor others still searching for an answer to this issue: local and just use the host name but that can be problematic. local part requires you add the avahi-daemon package to your server. Keep smb.conf as it is but have the client ask for the server and share explicitly either through Connect to Server or in the Location bar as Then restart smbd: sudo service smbd restart Just so I understand the question: You are trying to access Ubuntu Server 20.04 from another Linux client? If that is so it won't work by default.Įdit /etc/samba/smb.conf and under the workgroup = WORKGROUP line add this one - NT1 is samba speak for SMB1: server min protocol = NT1
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |