All my media is on 9 shared drives on a W7 PC the PC is known as THA-TV
In the origanal version of vero all I did was brouse to THA-TV entered my username password and all 9 drives showed fine - My Shield Amazon prime and oppo work the same dead easy It would seem not so on this new version of vero that is a real shame
While I am willing to try little more I would be happer if you could tell me how to make the vero go back to how it was when I first used it. If that is no longer possable I will have to return it to the seller as not working any longer
Then the problem isn’t OSMC related. Something is borked on your network.
We didn’t remove share support.
Security advisories were released which disabled browsing support.
We follow security advisories. Otherwise, people’s devices would be vulnerable, and then you would quite rightly complain that your computer got infected / ransomware etc because OSMC wasn’t secure and was a weak point in your network.
SMB browsing has also been disabled in Windows by default. They are also about to remove SMBv1 support as @fzinken has shown you. Only legacy devices which haven’t been receiving updates (and are therefore a security risk) still support SMB browsing.
However: SMB browsing isn’t necessary to mount shares in Kodi. You can just enter the name of the computer; share name and your username and password manually. Alternatively, if it’s working on an older version of OSMC, you can restore a backup via My OSMC.
The fact that you cannot mount shares via fstab or Kodi, even on an older version of OSMC, suggests something else is at play here.
We would need to see your fstab contents to advise. You could change the username and password or create a new account so that you can post it verbatim.
I hope this helps and we can get you up and running promptly. I understand having to manually enter some details is ballache. The decision wasn’t taken lightly however. The fact that Microsoft, Red Hat and many other vendors have also killed SMB browsing should be an indicator of the severity of the security problem, as well as why removing support for this was necessary.
“sudo mkdir /mnt/THA-TV
sudo mount /mnt/THA-TV
I have know idea what that means or what I am supposed to do with it
“You could just go to Settings - Services - SMB Client and set it to SMB1 that should give you back your beloved function.”
If that will get my shares back great I will try it but I should have liked that info at the start of this problem
“Watch out for your next Windows update”
I use W7 so your advice does not apply here
“Then the problem isn’t OSMC related. Something is borked on your network.”
Sadly this is the standard answer when software goes wrong, blame somthing else , my network is working fine your Vero worked fine till I tried to load your latest version, In addition I have Kodi 17.4 running fine on a Amazon fire box & nvshield box, I can also see network shares on a W7 PC and a Oppo player so the fault must in in your box not my network
“You can just enter the name of the computer; share name and your username and password manually. Alternatively, if it’s working on an older version of OSMC, you can restore a backup via My OSMC.”
Where am I supposed to enter that info and what is the syntax I should use