Hi @sam_nazarko , I figured how to solve this:
Since 4.3.7, Samba enforces a new security schema to avoid man in the middle vulnerabilities, so if your’re using a Guest user configuration or (a common case) your Linux Samba server is too old and don’t support NTLMv2 with SPNEGO even if you are using user/password, well, you need to disable the new security schema. A lot of Linux NAS lost they support a couple years after released, so, if you can’t ssh or gain an alternative acccess you will be hit by this problem.
So…What to do?
A combination of several configs already mentioned in this thread.
/etc/samba/smb.conf, inmediatly after [Global] add:
client use spnego = no
client NTLMv2 auth = no
sudo service smbd restart and that’s it, solved without the need of special mounts.
IMPORTANT: Any partial modification not including both configs on both smb.conf files, will fail.
A suggestion: This could be a security optional somewhere in the OSMC Config addon. Enabled by default could avoid many problems for newbies and wifes, but for security freaks, the option of cleaning both sentences must to be available. A simple checkbox firing the changes will do it.
This was tested over my 2 OSMC Raspberry Pis but also on my notebook with Ubuntu 16.04.