I have installed a NAS, a Synology DS224+. It’s my first NAS, and I’m not very good at computer-things.
My old eGreat mediaplayer, I managed to get working with both my computer AND my NAS, but my Vero4K, that’s another story. It works just fine with my computer, and with the latest update I got the sound back as well. It “went missing” for a little while, but works fine now.
The NAS, however, I just can’t get access to. I can find it via SMB, and with NFS, but I keep getting “operation not permitted”. Why is that, and how do I “get permit”?
I’ve permitted everything I possibly can permit, and still the same “operation not permitted”.
Can it be something in Kodi that blocks me? I do get in with my older eGreat.player.
ther might be old information in your passwords.xml
SPNEGO login failed: The attempted logon is invalid. This is either due to a bad username or authentication information.
You could try rm /home/osmc/.kodi/userdata/passwords.xml and then try to connect again but be carefull if you use this file and info in ot also for other area’s.
Check as well the SMB version on NAS and Vero, the need to be the same. SMB V1 is not secure anymore.
I’m sorry guys, but that is way beyond my knowledge. I’m glad if I can get Samba to work.
The question is why it don’t. I’ll se if I can remove any old passwords.
Passwords removed, but still no access. I can tap on the catalogs, but there’s no reaction, nothing happens. This in NFS, in Samba I still hav’nt permit.
It sounds like a version discrepancy in SMB. I don’t know if the Vero has SMBv1 installed any longer due to security concerns. You may need to enable v2 or v3. I had to do that on my QNAP NAS to get it to work.
If you want to use smb guest login (and that is what I understood from your description), you need to activate the guest user on the Synology which is deactivated by default.
That’s it! Of course on the Synology you need to allow access for user guest to the shares which should be used.
But using the guest login means, everybody in your intranet accessing the NAS as this user can see what you share. More secure is to use a specific user and password
Let’s assume on the Synology
you have a share named ‘video’
a user ‘Holger’ was configured to have read access to this share; the user has a password
In the mediacenter you can setup the smb access as follows:
In the OSMC GUI goto Videos → Files → Add Videos → Browse → Add network location (at the bottom)
Ok, smb ist not successful although it should with the settings above and you have removed the passwords.xml.
Before suggesting to restart the kodi configuration from scratch, let’s try the nfs part:
On the Synology check whether you have set the file service NFS as follows but replace the domain name with the domain you use for your intranet; typically you set/find this in your router web GUI.
The share you want to reach with the OSMC device should have a similar configuration like shown below, so edit the NFS rule accordingly:
hostname: use 192.168.2.0/24 (read from your NFS screen shot above)
Explanation: This allows access for ALL clients in ip range 192.168.2; 24 is the CIDR notation of the subnet mask 255.255.255.0
Privilege: Either read/write or read only
NFS works user based but typically there is no user osmc on a NAS; choose map all users to admin so any file access gets the privilege of the NAS admin user
Security: sys or AUTH_SYS is the default, so NFS uses the client’s user name and group. Leave it that way.
Enable asynchronous IO: Allow parallel IO and prevent ping-pong IO. Enable this in any case!
I really can’t say what has changed, but now it seems to work with samba. I’m done for the evening, and will restart everything again tomorrow, but it looks promising.
Well, might be the Synology has cached something and the smb service on the Synology wasn’t restarted since no configuration change. Look at the first picture of my first post, you’ll find a clear cache button somewhere.
