Posts: 6
Joined: Nov 2015
Reputation:
0
Hello,
After recent SMB scare I have set min SMB protocol on my Synology NAS (updated to latest) to SMB2. Kodi 17.3 on updated and upgraded Kodibuntu stopped to see shares from Synology. I have edited global samba.conf adding lines abut min protocol
min protocol = SMB2
client min protocol = SMB2
client max protocol = SMB3
but it did not help. I switched over to NFS then, but for Kodi to browse a share I have to set squash option to "map all users to admin" on my NAS. Otherwise shares are listed, but do not work.
Now, what is worse: to have on my NAS dangerous SMB1 allowed or allow all users connecting to exposed NFS share admin privileges? Both are scary.
foormanek.
Posts: 4,498
Joined: Jan 2011
Reputation:
150
DaVu
Team-Kodi Member
Posts: 4,498
2017-05-27, 23:01
(This post was last modified: 2017-05-27, 23:02 by DaVu.)
add
client max protocoll = SMB2
to your global samba.conf
that should make the share available again, IIRC. Set this for your NAS as well.
Which SMB version is used on your NAS/Kodibuntu version?
Remember that Kodibuntu isn't supported anymore, as this OS has its flaws
Posts: 6
Joined: Nov 2015
Reputation:
0
on kodibuntu samba is 4.3.11-ubuntu
on NAS - do not know - latest delivered by synology. I do not fiddle with console there, all is done from gui and it works.
I have changed client max protocol = SMB3 to SMB2 in /etc/samba/smb.conf, restarted samba - and it still does not work.
What is your linux base for kodi? If SMB2 works for you then maybe I could reinstall mine.
Posts: 4,498
Joined: Jan 2011
Reputation:
150
DaVu
Team-Kodi Member
Posts: 4,498
So you have changed to max protocol SMB 2 on both...your NAS and your PC?
And that doesn't work? I really doubt that a bit as SMB 2 should be possible.
Posts: 7,649
Joined: Jun 2011
Reputation:
287
known issue. Once the server doesn't allow NT1 anymore, browsing shares doesn't work. This is a samba issue.
You can add shares manually by entering the correct path in kodi though. Already existing sources work as well.
Posts: 106
Joined: Jun 2012
Reputation:
0
you're probably better off skipping kodi's built-in nfs client and just using nfs4 mounted using autofs or fstab on the host, then mount readonly with root_squash and noexec and kodi will just see it as a directory not a remote share.
Posts: 1,397
Joined: Aug 2009
Reputation:
23
Use the GUI and use NFS. I my experience, NFS is both faster, more reliable, and more secure than samba.
Posts: 6
Joined: Nov 2015
Reputation:
0
NFS even with squash "all users to admin" seems to be better. Exporting shares from server as read only seems to prevent connecting users from doing any harm to server despite being virtual admins. And SMB higher than 1 seems to be not implemented in Kodi yet, as I have learned from a dev answering my post elsewhere, so there is no point in messing with smb.conf, global or local.
Thank you all for attending.