Windows 10 issue - smb share no more work.......
#1
i have a folder shared from my pc.

This reach at smb://192.168.1.2 (My PC IP)

On my Pi2 i have the latest OSMC build........ i have try to add a source using this but immediatelly after i put all value i obtain an errors says:
Operation not permitted

Whitout any explanation....... on log it's say this:
Code:
21:13:28.121 T:1663062784   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192.168.1.2/'
                                            unix_err:'1' error : 'Operation not permitted'
21:13:29.402 T:1926175232   ERROR: GetDirectory - Error getting smb://192.168.1.2/
21:13:31.493 T:1671451392   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192.168.1.2/'
                                            unix_err:'1' error : 'Operation not permitted'
21:13:33.219 T:1926175232   ERROR: GetDirectory - Error getting smb://192.168.1.2/
21:13:35.049 T:1645761280  NOTICE: Universal - An Addons Toolkit: -watchhistory- -Loading sqlite3 as DB engine version: 3.21.0
21:13:35.096 T:1645761280  NOTICE: Universal - An Addons Toolkit: -watchhistory- -
21:13:36.281 T:1696879360 WARNING: CSkinInfo: failed to load skin settings
21:13:47.028 T:1671451392   ERROR: GetDirectory - Error getting
21:13:59.799 T:1663062784   ERROR: Previous line repeats 2 times.
21:13:59.799 T:1663062784   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://DIABOLIK-PC/'
                                            unix_err:'1' error : 'Operation not permitted'
21:14:01.186 T:1926175232   ERROR: GetDirectory - Error getting smb://DIABOLIK-PC/
21:14:01.186 T:1926175232   ERROR: CGUIDialogFileBrowser::GetDirectory(smb://DIABOLIK-PC/) failed
21:14:05.397 T:1926175232   ERROR: GetDirectory - Error getting smb://
21:14:05.402 T:1926175232   ERROR: CGUIDialogFileBrowser::GetDirectory(smb://) failed
21:14:10.166 T:1663062784   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192.168.1.2/'
                                            unix_err:'1' error : 'Operation not permitted'
21:14:11.485 T:1926175232   ERROR: GetDirectory - Error getting smb://192.168.1.2/
21:14:11.486 T:1926175232   ERROR: CGUIDialogFileBrowser::GetDirectory(smb://192.168.1.2/) failed
21:15:45.802 T:1926175232  NOTICE: Samba is idle. Closing the remaining connections
Nothings it's explain.

I have also try to add a user on my windows 10............. i have created a user osmc whit password osmc. I have restart my Windows 10 but never change........... on osmc it's impossible to reach this shared folder.

How it's works ?


*EDIT*
I have tested and tryed to access to this smb shared folder from my android phone used a file manager. All it's works whitout any problems....... i need only to put my username and password used on windows logon. I have also tryed to add this newest "osmc" user created and it's works whitout any problems.
Only on kodi this folders it's not works............
...only on your "little world" can you lay down the law...
Reply
#2
(2018-05-11, 21:19)DjDiabolik Wrote: On my Pi2 i have the latest OSMC build
"Latest" is not a version. So many users claim to have the latest version, and it turns out they don't (anymore).

If your Win10 pc was recently updated with the Fall Creator Update (or something even newer), you now have been blessed with Samba v2 workings.

That means the user sharing the files MUST have a password. Also, network browsing is no longer supported.
Both of these measures are security updates.

So, double-check your video source(s) and their user credentials. If you haven't used password before with Samba, you will now.
Reply
#3
This is the osmc build i have:
Code:
Info sul kodi.log:
21:28:17.444 T:1925949952  NOTICE: Starting Kodi (17.6). Platform: Linux ARM (Thumb) 32-bit
21:28:17.444 T:1925949952  NOTICE: Using Release Kodi x32 build (version for Raspberry Pi)
21:28:17.444 T:1925949952  NOTICE: Kodi compiled Apr  3 2018 by GCC 6.3.0 for Linux ARM (Thumb) 32-bit version 4.9.30 (264478)

Info VERSION_ID:
VERSION_ID="2018.04-2"

About windows 10.......... i have the latest patch 1803 installed about two days ago.

On Windows 10...... i have a password setted from both account! The daily password used for windows and i have also add a addictional user called "osmc". But on Kodi it's not works.......... immediatelly after put value to add the smb share i not obtain the request for password but the "Operation not permitted" it's immediatelly brings on screen. I can't do nothigs.


*EDIT*
Wait a moment......... by google i have found this pics:
Image

I have take a look on my OSMC Setting........... i have found it's setted to SMBv3 !

I have try to SET like it's setted here.......... i have set SMBv1. OSMC has says need to restart to apply. I choose ok and at the restart! BOOOM!! It's works!
The form for put password it's be appears........ i have insert the combination of username/password created and it's works! The shared files now it's works!

After that i have try to set this value to SMBv2 ! Another restart and boom again!
It's works!

After i try to set this to SMBv3............ but i don't thinks this works.

Problably windows not use SMBv3 and this create this issue ??
...only on your "little world" can you lay down the law...
Reply
#4
(2018-05-11, 21:48)DjDiabolik Wrote: "Operation not permitted"
That is usually shown when doing network browsing in Kodi...
If you use "Add a network location..." to create a new SMB source, and put in all necessary credentials, things should work.™
Reply
#5
(2018-05-11, 22:10)Klojum Wrote:
(2018-05-11, 21:48)DjDiabolik Wrote: "Operation not permitted"
That is usually shown when doing network browsing in Kodi...
If you use "Add a network location..." to create a new SMB source, and put in all necessary credentials, things should work.™  

mmmmmmmmmmmm... yeah i have tryed also.

Read my EDIT above up here....... problably i have found the issue.
...only on your "little world" can you lay down the law...
Reply
#6
Setting your network back to SMBv1 compatibility is the wrong solution. Unless you do want to invite WannaCry-like attacks onto your local network.

The choice is yours.
Reply
#7
(2018-05-11, 22:33)Klojum Wrote: Setting your network back to SMBv1 compatibility is the wrong solution. Unless you do want to invite WannaCry-like attacks onto your local network.

The choice is yours.
 But if SMBv3 it's not works.............. i don't have alternative.

For now i have set SMBv2.......... for Wannacry attack a thinks you need to connect to my lan or my wi-fi router...... it's correct ?
...only on your "little world" can you lay down the law...
Reply
#8
SMBv2 is sufficient to be safe from WannaCry.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#9
(2018-05-13, 19:12)Milhouse Wrote: SMBv2 is sufficient to be safe from WannaCry.
 Yeah.. thanks for info but yesterday on OSMC on the image preferences i have re-select SMBv3 and apparently now the windows shared folder it's reachable right now (i have tryed about 30 minutes after i have reselect smbv3 about 24hours ago).
At this point i need to see if this issue re-appears on my setup but at this point i don't know if the issue it's related about windows of in kodi setup.......
...only on your "little world" can you lay down the law...
Reply
#10
This SMB issue is starting to get to on my nerves.

A few months ago I was able to access the shared folder in windows 10 from my RPi3 using the following address : smb://192.168.100.2:445/ ( this was a fix/workaround? I found earlier that was able to access windows 10 folders )
Now whenever I try to access it I get a "Connection Refused" message when I use the Horizon skin, the message in the default skin is "No route to host"

I use latest Librelec 8.2.5 (( not sure how to copy the log from RPi to Windows ))
Reply
#11
Did the Windows machine just update to build 1803? If so check the sharing settings again, as on my machine it reset everything and removed SMB1 again.
|Banned add-ons (wiki)|Forum rules (wiki)|VPN policy (wiki)|First time user (wiki)|FAQs (wiki) Troubleshooting (wiki)|Add-ons (wiki)|Free content (wiki)|Debug Log (wiki)|

Kodi Blog Posts
Reply

Logout Mark Read Team Forum Stats Members Help
Windows 10 issue - smb share no more work.......0