Greetings, I had OSMC working with my Win 10 machine for some time, however I would often get ‘unable to update library’ errors, so I decided to scrap my shares and update both the server and OSMC.
I saw a post about using ‘fstab’ to configure shares that way, and this was the method I ended up using to get RetrOSMC to find my networked roms. That aspect of things works fine.
After modifying the fstab file, from SSH, I am able to view my network shared folders and see the contents of them, however back in OSMC, I’m unable to find or view them in the “add sources” option.
What am I missing?
(Currently away from home, so logs are not possible until tonight)
As long as the “Network Discovery” service is running on the Windows system (and it is enabled by default), browsing of SMB shares works fine with Windows all the way up to Windows 10.
The trick is that the default in Windows 8 and up is to not allow non-authenticated users to browse shares. This can be changed, and again, browsing works.
Overall, though, the correct way to deal with it would be for OSMC to have a configuration that allowed the entry of a username/password that would be used to authenticate on the Windows network, and then browsing would work. Also, for those of us with Active Directory domains, allowing the OSMC box to join the domain would also solve the problem, once an “osmc” user is created in the domain.
Another tid-bit of information that might be of use:
After setting up the fstab / CIFS information, and confirming that I can browse that content, I restarted and popped back into OSMC. From there I attempted to browse to /mnt where those fstab directories are mounted to, and it will not load. I get a ‘buffering’ log come up, but the directory will not list. I tried waiting over 5 minutes without luck.
Sorry to object, browsing is a feature of SMB1 which will be automatically be disabled by the latest Windows 10 upgrade if no smb1 client connects within 14 days after the update
While also smb1 was disabled in OSMC as default and would need to be enabled in settings if required
Well you then could force it in Kodi under Settings - Services - SMB Client - Max Protocol.
But to be honest I would leave that as it is and try to fix the fstab mount
I went through this with Windows Server 2012 R2 (the server version of Windows 8.1), which has SMBv1 disabled by default out of the box. All modern Windows (7 and above) could browse the server just fine, but anything older needed SMBv1 enabled, and needed to have an authenticated user configured.
I have no idea how this affects Samba-based systems like Linux, but obviously it’s possible to browse even a pure SMBv2 or v3 network, since Windows does it, but I suspect it needs an authenticated user.
I understand that, I just was asking where in OSMC you are not seeing them. When it is at the stage of “Add Source” it is normal that you don’t see the files as at that stage only folders are shown
I didn’t have the option to manually enter a directory, it was greyed out. Weirdly enough, I enabled logging, restarted, and went back to Add Source. This time I still couldn’t see my network, but I was able to direct it to the /mnt/ path and add them there.
It all seemed to work fine. After dropping back to the menu, all of my TV shows appear to be there and workng fine.
My movies though, will not populate. I get a “couldn’t download information - could not connect to remote server” error. This is goofy, as my TV and Movies are on the same PC.
This error mentioned above, is what I was getting in the past, essentially preventing my media from updating.
That did it. I confirmed first by removing that as my scraper from my shares and my media appeared. I then went in and discovered my outdated add-ons. Updated TMDB, scraped again, and everything works. Thanks again for the assistance.