2020-07-16, 22:44
I've been using Kodi for a number of years, to pull media from a shared computer drive, and I've always had a great time with it.
Never had any trouble connecting to the drive or having Kodi browse my network for content. Up until last week...
Last week, I swapped out my crappy, provider-supplied Android TV box for an Nvidia Shield Pro.
So many things are better now, but I hit a snag after installing the recent Kodi. This problem seems to be a really popular one, but nothing I refer to has helped me to resolve it.
Obviously, the ability to detect and freely browse my network has been removed. Looks like only SMB2 is supported by Kodi.
(I have all 3 levels of SMB enabled on my computer and in Kodi.) No more letting Kodi just find and open what you've already given permission to access.
It's now necessary to input all the network pointers and even user names and passwords. I get that, but it seems this method doesn't work as intended.
I have tried every form of syntax to add my media drive as a network location - IP addresses, server name, shared network path, user+password, no user no password, Windows backslashes, Android forward slashes, on and on - nothing seems to make Kodi happy.
I have given every possible permission to my drive (more permission than I feel is even sensible). Technically, a user and/or password shouldn't even be necessary, but I still give them to Kodi. I've turned off my firewall. I've made sure my VPN service was off. I've checked for any port forwarding issues on my router (though no port forwarding should be an issue with port 8080, which Kodi uses for this). I've looked for every possible thing I can think of that would stop Kodi from seeing my network shares, and I've drawn a blank.
To clarify, I can access everything from outside of Kodi. Other apps on the same device have no trouble getting at my files.
What is going on with Kodi, Windows SMB and shared drives??
If there's a specific syntax that is needed, in order to add a network source, it would be helpful to have that syntax defined and explained more clearly. I'm no stranger to network protocol, but my experience is not helping me see the solution here.
Never had any trouble connecting to the drive or having Kodi browse my network for content. Up until last week...
Last week, I swapped out my crappy, provider-supplied Android TV box for an Nvidia Shield Pro.
So many things are better now, but I hit a snag after installing the recent Kodi. This problem seems to be a really popular one, but nothing I refer to has helped me to resolve it.
Obviously, the ability to detect and freely browse my network has been removed. Looks like only SMB2 is supported by Kodi.
(I have all 3 levels of SMB enabled on my computer and in Kodi.) No more letting Kodi just find and open what you've already given permission to access.
It's now necessary to input all the network pointers and even user names and passwords. I get that, but it seems this method doesn't work as intended.
I have tried every form of syntax to add my media drive as a network location - IP addresses, server name, shared network path, user+password, no user no password, Windows backslashes, Android forward slashes, on and on - nothing seems to make Kodi happy.
I have given every possible permission to my drive (more permission than I feel is even sensible). Technically, a user and/or password shouldn't even be necessary, but I still give them to Kodi. I've turned off my firewall. I've made sure my VPN service was off. I've checked for any port forwarding issues on my router (though no port forwarding should be an issue with port 8080, which Kodi uses for this). I've looked for every possible thing I can think of that would stop Kodi from seeing my network shares, and I've drawn a blank.
To clarify, I can access everything from outside of Kodi. Other apps on the same device have no trouble getting at my files.
What is going on with Kodi, Windows SMB and shared drives??
If there's a specific syntax that is needed, in order to add a network source, it would be helpful to have that syntax defined and explained more clearly. I'm no stranger to network protocol, but my experience is not helping me see the solution here.