In the add network location for the path enter just the ip itself for the server name and nothing else on that line (the smb:// gets added by the protocol option above it) and you will likely have the best luck with using credentials. You may also need to go into settings>services and set the SMB version to min/max v1.
It may also be possible that there is some incorrect credential info that got set along the way that may be causing issues. I would ssh into your device and take a look in ~/.kodi/userdata/passwords.xml. You should see where and how it is adding the credentials to the network path so you can judge if their is an error.
Thank you for your help. Unfortunately, it still doesn’t work.
I didn’t type myself “smb://” in front of my IP address, iy has been automatically added by the system, as you explained.
I forced SMB1 protocol in the settings but I still get the same result.
I saw nothing wrong in the passwords.xml file.
I really don’t understand why it doesn’t work although it works perfectly on my other devices.
Prior to this I did install the smbclient on my Vero4k+ to check the the visibiity of SMB served shares to Kodi ussing the SSH shell. They were all visible for all versions of SMB.
(e.g. osmc@Kodi: smbclient -m smb3 -U -L
My Windows setup is straight forward, the folders exposed by SMB are ‘shared’ using the Advanced sharing option with the security group ‘everyone’ given read permission. Obvioulsy you will still need to an account with priviliges to log into when connecting to the SMB server from Kodi.
I know from previous experience that SMB has been flakey for various clients over the last 10 years or so (with devices I have, e.g. Oppo BDP-103) i.e. they would be fine with SMB protocol
until microsoft did an update. So I moved to upnp/dlna using UMS (which I recommend if configured properly), and now I am trying SMB again -
I have not even checked on the performance but I suspect it will probably be OK on my set up, particularly as I have mesh wifi which can cope with reliable Wifi connections up to around 300 Mpbs.
In addition to what fzinken stated you should be aware that Win 10 has an automatic system for purposely removing SMBv1 after a period of time that can’t be turned off forcing you to reinstall it again periodically.
Now that you have some sources setup if you set Kodi’s network settings to min/max SMBv3 do these existing sources continue to work?
Security at the expense of functionality, twas ever thus.
All these attributes of the design & implementation of a system influence each other, i.e. security, flexibility, configurability, functionality - I digress.
Performance wise, I didn’t notice any change when compared with UPNP/DLNA performance and inparticular rendering a 4K UHD ATMOS/TRUEHD movie in an .MKV container.
Agreed SMBv1 is probably less secure than SMBv3, but using SMBv1 (with legacy security setting) was the only way to detect a SMB server on my Win 10 PC.
I tried switching back to SMBv3 since and Kodi was not able to see the SMB Server, or perform a succesful library scan check (I checked the Kodi Log, its full of ‘Unable to open directory’ ERRORS). Similarly I dont see any SMB* server when trying to add a network location in the Kodi file manager, I have to switch back to SMBv1.
During the installation of SMBv1 on Windows 10 there is an option to install or rather NOT install the ‘SMB 1.0/CIFS Automatic Removal’ tool, which as far as I understand, if present, is how SMBv1 may be automatically removed - so, I didn’t install it. See also:
Automatic removal of SMB1 after 15 days is a one-time operation. If an administrator re-installs SMB1, no further attempts will be made to uninstall it.
Given the points above, I think perhaps somebody needs to look at the way Kodi is using the smbclient library, or does the debian distro smbclient library need to be fixed/updated, to be brought uptodate with microsoft SMBv3 ?
(from my Vero4K+ log file - libsmbclient:armhf 2:4.9.5+dfsg-5+deb10u1 - shared library for communication with SMB/CIFS servers).
Discovery for SMB only works when using v1. For SMBv3 one can go to videos>files>add videos>browse>add network location> and select SMB, add the ip address (or machine name) of your file source (and nothing else) in the “server name” field and the username and password then click OK. This will give you a new network location that is browsable so all your sources can just be added with videos>files>add videos>browse>[server ip (or machine name)]>
I assumed that when you had connected using SMBv1 there was one or more Kodi sources that you had added and maybe some items that you had scanned into the library. I was asking if, for example, a movie that you added to your library and verified it played using SMBv1 was still working if you switched to SMBv3. The not being able to see the server by just browsing the network when you switch is expected.
Just for context, I personally use an up to date Win10 PC using SMBv3 and other than the lack of network discovery, I have not run into any issues communicating with OSMC.
If the improvement you seek is the function of being able to browse available smb shares from within Kodi, you will be disappointed to know that it’s Microsoft who removed this ability when they deprecated smb1. Kodi cannot improve this.
Nevertheless there is still a compatability issue between Kodi and SMBV3.
I have other devices (e.g. Android phones) which can connect with SMBV3 and see at least the PC Name, with which to authenticate.
In my (user) experience SMBV1 works best with Kodi (18.9), and still requires authentication (if your Win PC is setup properly) so there is some ‘security’.
Kodi/Vero4K should support SMBV3 better, as I’m sure many users use this interface - but then who am I to say what should be improved in Kodi/Vero4K.