![]() ![]() 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. 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. ![]()
0 Comments
Leave a Reply. |