If your source is providing NFS natively,
it's better to set LE/CE to use NFS shares in OS - mount them on OS level.
Kodi has NFS functionality, but, IMHO, it's like an addon, which works relatively slower and buggier...
If your source is providing NFS natively,
it's better to set LE/CE to use NFS shares in OS - mount them on OS level.
Kodi has NFS functionality, but, IMHO, it's like an addon, which works relatively slower and buggier...
Now you've put doubt in my mind again!
As windows doesn't support NFS natively I guess SMB is the way to go.
Theoretically, since some updates, Windows 10 should work with NFS.
My experience shows that 10 Enterprise eats NFS shares, Pro - freezes to the point of rescue mode and the only remedy is to remove the NFS services in this emergency mode.
The above is said about Windows 10 as NFS client.
It seems rather pointless to me to set Windows as an NFS server, stick with SMB and if you're adamant to use SMB v2/3+ shares without credentials, there is a registry crack/hack/fix for it.
imho, if you run a windows server use smb, if linux then nfs.
It's damn easy with macOS, install free NFS Manager then point and click.
Then in Kodi all that is needed is to select Zeroconf and all the hard work is done.
I don't know what it means to use SMB shares with credentials!
I don't know what it means to use SMB shares with credentials!
to add an username/password
only SMB1 supported an "guest" account/access with no passwords etc
Theoretically, since some updates, Windows 10 should work with NFS.
It works, but not very well (windows 10 enterprise)
As of August 15, 2018 it still does not work.