Posts: 2
Joined: Oct 2021
Reputation:
0
I too have an old SMB 1 device as my media NAS. I was able to get it "working" using the above methods both in Kodi and in VLC on my Android TV, latest everything. Initial load of any media is slower than normal. With certain media types, (mainly DVD menus) I have stuttering -- but once the main program starts, everything's suddenly and oddly fine. I can skip around and it rebuffers near instantly. Everything's great.
But...
Eventually, and never during playback, the drive will disappear. I'll get "Playback failed" when trying to play a different file from my library, and "Error: Software caused connection abort" followed by "Remote share: Couldn't connect to network server" if I try to browse or scan the drive. While in this state, nothing can access the drive, not other apps on the Android TV system, nor any other device on the same network.
If I wait long enough, the problem goes away on its own. But make enough access calls via Kodi (loading or scanning a larger folder in the file browser brings on the problem rapidly, for example) and it will return. None of the other devices on the net, including an older Android/Kodi combo, cause this issue.
Is there some setting unique to Android TV that could be trying to make each access request as a new connection or too rapidly or some such and overloading my NAS? It's not just a SMB1 problem as all the devices are using SMB1 to access it and only the Kodi 19/Android TV triggers the issue.
Posts: 171
Joined: Dec 2020
Reputation:
20
When I was running Kodi 19.1 on my Sony TV, I couldn't get SMB working either. However in the file requester there was "zeroconf" option which actually worked, I could even browse to my shares through that.
Now I have Shield Pro. I haven't tried SMB mounting inside Kodi, instead I mounted everything globally in Shield settings.. works nicely. You need to add the NAS permission if you want write access, that wasn't instantly obvious.
Posts: 1
Joined: Oct 2021
Reputation:
0
Working in Sony Tv - Smb 2, Smb 3
1. Add source
2. Browse
3. Add network location
4. Set ip address
5. Set fake username: adm and password: adm
Posts: 2
Joined: Nov 2021
Reputation:
0
Hi Guys!
Just wanted to share an interesting behaviour/solution for a somewhat same situation.
The system is: Win2019 server with smb2, shares protected with user+password, Chromecast with google TV and Kodi 19.3.
Fresh installation, set up everything with the default SMB Client settings, no biggie, everything worked just fine.
Just for fun I set the minimum smb version from none to SMBv2 in the smb client section and all hell broke loose.
Share no longel accessable with "Operation not permitted" error. (did not add the share again, it just stopped working right away)
Removed the share from kodi, added again. Still not working.
Exit/restart kodi, chromecast. Nope.
Okay, thought I. Enough with the experiment. Settings/SMB Client minimum version set back to none and it should work.
But it did not.
I tried many things:
- exit/restart kodi, chromecast, server
- removed the share from kodi, added again
- checked the share acces from another machine (worked fine, from windows, and from android as well)
- tried with ip, domain name, with and without share name. no help.
I was in the brink of remove and reinstall kodi, but tried one more thing:
In smb client settings i hit "Reset these values to default"
To be fair, at that point during the tests and tryouts it is may be at minimum version v2, but it seemingly just set it back to "none".
And lo and behold it started to work again.
So long storry short: Set back to "none" did not work, but resetting values did.
I don't really know what internal values it may reset as well other than the ones accessible in the ui, but it probably did something.
I hope it will help somebody, or it will shed a light on some internal bug maybe, but i tried my best to share my expreiences.