Posts: 3
Joined: Jan 2016
Reputation:
0
Got referred to this thread from Reddit. Go figure my first time setting up Kodi was after MS jacks up SMB with an update. I was, and still am, pulling my hair out on this. At any rate below is a copy / paste of a post I did on Reddit detailing everything i've done thus far. Tonight i'm going to take a closer look at Homegroups, as i didn't take some of the steps detailed here, along with trying a fully qualified path to the share. Will report back if I make any headway.
I'm running OSMC on a Raspberry Pi B+ and Windows10. I've tried everything i can think of and / or Google and i'm still getting wonky behavior. To be more specific if i add a video source i can browse and see my shared folders just fine; the problem being is that usually they don't show the contents being about a dozen or so video files. If something does show up its usually the first three items in the folder which, incidently, i am able to play back fine from the movie library section even whilst getting the 'invalid argument could not connect to network store' message when navigating the videos > files section. There was one brief, shining moment where everything showed up properly in the videos section and then a moment later it was gone, meaning the videos > files > shared folder contents were once again blank and i was bombarded by 'argument invalid' errors. Now the interesting part is if i continuously select the shared folder from the UI i will usually get 'invalid argument' message, however if i just keep selecting it i'll either get an empty folder or i'll get the first three, and at one point, four items from the list which i can play back.
So on the OSMC side here are the paths that i've tried, and honestly they mostly all have the same 'works some of the time but not usually' result, although interestingly if something makes it into the 'movie' library I can always play it back-
smb://hostname/Users/Me/Videos/
smb://ipaddress/Users/Me/Videos/
smb://hostname/Videos/ (this path occurs when using browse rather than manual entry)
smb://ipaddress/Videos/
smb://user:pass@ipaddress/Users/Me/Videos/
smb://user:pass@ipaddress/Videos/
As i write this i'm realizing i never tried a fully qualified path so i'll probably try that tonight. Although the fact that is sometimes sorta works makes me think its not going to be a path issue. Something like- smb;//user:pass@ipaddress/C:/Users/Me/Videos/
Now over to the Windows side-
Create Homegroup
Join Homegroup
Create local user (for user / pass)
Share folders, the go into advanced sharing on the folder and tick off the 'Share this folder' box
Increase IRPStackSize in registry (key didn't exist, had to add, made the value 15 or thereabouts, going to try increasing further tonight)
Increase size parameter from 1 to 3 in registry
Things i haven't done as they seem silly although i might later on tonight just to see what happens-
Disable firewall
Disable defender
I'm kind of feeling that the issue has to be on the Windows side as the setup from Kodi is so straightforward. The 'sometimes it works, but poorly' aspect is throwing me though so i'm not entirely sure. Any thoughts would be appreciated.
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
IIRC, kodi 14 still used samba 3.0, so smb protocol 1 (or 2) only.
So downgrading has the same effect as disabling smb 3 on the windows machine.
Posts: 87
Joined: Jan 2016
Reputation:
0
UPDATE: I managed to get mine working again by uninstalling win10 1511 and then in KODI I manually typed in the network path for the folder. As with others, not sure if this workaround will do it for everybody but its worth a try. I'm going to try later in the week updating win10 to 1511 and see if that breaks the connection again
). Now I can again browse non-windows samba shares via windows explorer and kodi. Doesn't look like there's an easy way to roll back to standard windows 10, so I'm stuck running beta MS software on this PC for the time being - yay!!!
