[Tarbipoo]

MrMC uses a different SMB implementation.

I still don't get your 404 internet access errors, cause they are SMB unrelated.

Ah I see - so with Kodi is there any way to replicate or change the SMB implementation or is it too intrinsic to Kodi's framework?

I've reviewed the logs and have not seen any 404 errors since the first logs I posted, so I am hoping that was a unfortunate timings with possible network issues. Happy to post further logs if needed!

[fritsch]

Can you switch to NFS somehow?

[Tarbipoo]

Can you switch to NFS somehow?

Unfortunately not - the router that are hosting the SMB shares gives you no option at all. My only confusion is why Kodi 18.5 on my 2017 Shield works fine but not Kodi 18.5 on 2019 Shield. May suggest that the Shield O/S has made changes as to how it handles whatever implementation Kodi has of SMB given MrMC SMB implementation is OK?

FYI - tried the Kodi settings for SMB client min/max level down to SMB v1 and allowed legacy security - did not make a difference.

[fritsch]

While it is not optimal at all

USB Sharing: Support Samba (Storage) / FTP Server / Media Server / Printer Server, 3G/4G
Modem / SFTP Server / Web Storage

Could you expose it via ftp or web storage (http?), Media Server is UPNP right?

[Tarbipoo]

While it is not optimal at all

USB Sharing: Support Samba (Storage) / FTP Server / Media Server / Printer Server, 3G/4G
Modem / SFTP Server / Web Storage

Could you expose it via ftp or web storage (http?), Media Server is UPNP right? 

Yeah I am sure uPnP is Media Server and that didn't work. Let me see if I can setting up via FTP

[fritsch]

Make triple sure it's not exposed to outside world :-)

[Tarbipoo]

Make triple sure it's not exposed to outside world :-)

FTP in enabled, FTP (over Internet) is disabled. Anything else I should check - this isn't my area of expertise! Can look into it though as it looks promising - no crashing what-so-ever. I'd would have seen a crash by now but videos play without issue. 

Just wondering if you know, any disadvantages of using FTP against SMB and is it better to go HTTP or FTP

Thanks for all your help!

[fritsch]

Long story short. If you have http vs. ftp vs. smb in a local network and all were fine I'd definitely use smb. But this is not the case here and we need to find a workaround for you.

FTP is very good if you read files ahead, e.g. start at the beginning, continue towards the end, it was intended as a file transfer protocol. Seeking forth and back might not work that great. HTTP has Range and FTP would have REST for that internally, but I don't think kodi makes any use of this.

Try some edge-case files: 4K UHD with DTS-HD Audiotrack or something and if it works - don't look back :-)

[fritsch]

Something to add: If it works - it will work forever :-) cause the implementation is from libcurl and used directly.

[Tarbipoo]

Something to add: If it works - it will work forever :-) cause the implementation is from libcurl and used directly.

So...sorry to be a pain. Everything works great on FTP (except one thing) and I cannot get HTTP to work. I am happy to go down the FTP route but an issue I have seen is that after an hour of not using Kodi and coming back to watch something...all media is considered no longer available and I get asked to remove it. If I go into 'Files' go the share, play the file from there, then go back to the orginal 'Tv Shows' location in Kodi it works. Almost like I need some kind of keep alive? Any ideas? Never had this with SMB

[fritsch]

Sorry - no idea for that. If the router does not have a setting for "keep alive" I am also out of ideas.

For http: Can you access the shared files via a browser? If you get that going, the process for kodi is simple.

[Tarbipoo]

Sorry - no idea for that. If the router does not have a setting for "keep alive" I am also out of ideas.

For http: Can you access the shared files via a browser? If you get that going, the process for kodi is simple.

Yeah trying HTTP to see if that works better but struggling (thought it would be simple). I can access the files via a browser using 192.168.1.1:8082.

However, in Kodi, I try to add the source using the option 'Web Server (Http)' setting the address to 192.168.1.1 and the port to 8082 -> Kodi does not find any source. Something I am doing wrong?

[fritsch]

The http source is not so funny to add. As a hint: check after you filled out the fields when kodi displays the full url.
Alternatively check sources.xml in your userdata folder in /sdcard/..../org.xbmc.../.kodi <- the .dot before kodi is often overssen. Here check if the url you see in the file makes sense.

[Tarbipoo]

The http source is not so funny to add. As a hint: check after you filled out the fields when kodi displays the full url.
Alternatively check sources.xml in your userdata folder in /sdcard/..../org.xbmc.../.kodi <- the .dot before kodi is often overssen. Here check if the url you see in the file makes sense.

It looks like it makes sense to me...

-<source>
<name>Router</name>
<path pathversion="1">http://192.168.1.1:8082/</path>
<allowsharing>true</allowsharing>
</source>

Unless something is missing? It just comes up with no files or folders when accessing that source

[fritsch]

I just tested on my system.
I chose add new location and entered: http://jabba/~fritsch/  - gave it the name fritschwww - and it worked like a charm

        <source>
            <name>fritschwww</name>
            <path pathversion="1">http://jabba/~fritsch</path>
            <allowsharing>true</allowsharing>
        </source>

Only difference I see is the port. But your's looks correct as well