SwanStream 64 Posted May 9, 2017 Posted May 9, 2017 I posted a poorly asked version of this over in the synology sub. https://emby.media/community/index.php?/topic/47311-slow-migration-to-a-nas/ I'm trying over here in the Kodi sub because I suspect the answer lies in how Emby-for-Kodi is handling things. At the moment I've got a PC emby server, a PC kodi with emby app as client and a nvidia shield as client. I'm adding a Synology NAS as storage. So Some files live on the PC server and some on the NAS. Both clients can find all files on the PC server. Paths for those sources are simple UNC \\Server\share format and work well on both clients Using the UNC path \\NASServer\Movies_1 as a source folder the pc client picks it up fine and runs with it. The shield does not. Giving 'file doesn't exist' error. If I add path substitution of nfs://192.168.0.136/Movies_1 the pc can't find the file and either can the shield. However, kodi on the shield can find the nfs path via it's library add and search the nfs network. So access is there and the shield can 'see' it but for some reason I don't understand emby for kodi can not. Any help greatly appreciated!!
Luke 42078 Posted May 9, 2017 Posted May 9, 2017 hi, what do you mean path substitution? where did you do that?
SwanStream 64 Posted May 9, 2017 Author Posted May 9, 2017 hi, what do you mean path substitution? where did you do that? my bad... I think many moons ago it was called that... now it's: on Server dashboard, library, movies, manage folders, (Optional) Shared network folder:,
SwanStream 64 Posted May 9, 2017 Author Posted May 9, 2017 If I remove the path substitution the file plays from the PC, so from that perspective it is.
SwanStream 64 Posted May 10, 2017 Author Posted May 10, 2017 Update: Some progress, problem(s) sorted, but I don't like the answer! Turns out it was all permission issues on the Synology. In case this helps someone else here's the scoop in my case. Windows 10 emby server and some file serving. Windows 10 kodi w/emby app client Nvidia Shield - Kodi w/emby app client Synology DS2415+ Diskstation file serving On the Emby Server source folders are setup as UNC paths: for the Windows10 PC shares - \\SERVER-PC\SHARE for the NAS shares - \\SERVER-NAS\SHARE path substitution isn't necessary (for me) on PC shares for the NAS shares I have setup NFS path substitutions as nfs://ip.add.re.ss (of NAS)/volume_name/Share_name i.e. nfs://192.168.0.136/volume1/TV_1 On the diskstation. Control Panel Under File Services SMB/AFP/NFS - Enable NFS Under Shared Folder - Share_name (TV_1 in my case) Edit Permissions - Give user Read/Write NFS Permissions - Add clients by their IP address, privilege - Read/Write, Squash - Map all users to admin, Enable Asynchronous, Allow from non-privileged ports, allow users to access mounted subfolders Under User Edit applicable user User groups - add administrators I'm not sure if it's necessary but in a suspenders and belts effort I also enabled read/write under permissions for applicable shares under the user. I don't really have a good handle on Synology security and it really, really rubs me the wrong way that I can't seem to give access short of the keys to the kingdom for this configuration to work. If anyone has suggestoins please do let me know. Why NFS over SMB? Although I do have smb access from various android devices to the NAS, NOT from within Kodi on the shield for some reason. it has eluded me. This NFS setup does work from both devices it seems. Superficial testing is all that I've done for now.. Hope this write up helps someone else with the same brickwall imprint on the forehead! Suggestions on a cleaner setup more than appreciated!
Angelblue05 4132 Posted May 10, 2017 Posted May 10, 2017 Have you tried using the static ip rather the server name for your smb paths? Sent from my iPhone using Tapatalk
SwanStream 64 Posted May 10, 2017 Author Posted May 10, 2017 Have you tried using the static ip rather the server name for your smb paths? Sent from my iPhone using Tapatalk in the path substitution yes. ex. nfs://192.168.0.136/volume1/TV_1 is working smb://192.168.0.136/volume1/TV_1 is not working I haven't tried as the 'native' folder path. Should I?
Angelblue05 4132 Posted May 10, 2017 Posted May 10, 2017 No. If smb is not working with addon paths then it will not work with native path. Instead you'd get file not found in Kodi. Sent from my iPhone using Tapatalk
Recommended Posts