Kosta 8 Posted June 26, 2015 Posted June 26, 2015 (edited) Hello, For some reason, I cannot play back from my Asus Chromebox with Openelec, but it's working in the KODI on the computer on which Emby Server is running. Everything seems to be installed correctly, Isengard Beta2 and Emby 1.0.14, including working shares. It used to work however, yesterday morning when I tested, all was fine, then through the afternoon I removed everything from the server yet again and let it rebuild everything, and now it's working quite well on the server-computer, but no go on my Asus Chromebox. Here is the log: Edit: Log removed. I am wondering however, I have the checkbox "Use HTTP instead of SMB" NOT checked, and yet it writes "HttpServer: HTTP Response". Should there by HTTP if I don't have it set? Edited June 26, 2015 by Kosta
Angelblue05 4132 Posted June 26, 2015 Posted June 26, 2015 No, if you are within your home network, you don't need to enable play from http. However we would need a Kodi log, not an Emby log. Please see here: http://emby.media/community/index.php?/topic/17599-how-to-report-a-problem/
Kosta 8 Posted June 26, 2015 Author Posted June 26, 2015 (edited) Deleted. Edited June 26, 2015 by Kosta
Kosta 8 Posted June 26, 2015 Author Posted June 26, 2015 (edited) Sorry, now the correct one, containin the Emby Info Log. To recreate I tried playing back couple of files in my main folder. Log removed. Edited June 26, 2015 by Kosta
Kosta 8 Posted June 26, 2015 Author Posted June 26, 2015 Hmmm, something very weird I noticed - it attemped playing WAY more files than I clicked. I clicked like the first 5 in the succession of some 10seconds or something. But then it went up to some 20-30 files down the list.
im85288 1493 Posted June 26, 2015 Posted June 26, 2015 Without having looked at your log I'm guessing your paths on the server are not set up using upnp? If that's the case you can either fix the paths on your server to use things like //server/share or you can use the stream over http option on those clients that are not on the same machine as the server
Kosta 8 Posted June 26, 2015 Author Posted June 26, 2015 Hmm, indeed, now that you mention it: I did change the library-paths from the mapped drive to \\IP-address\path. Since then apparently it has problems playing from the Kodi. So according to your comment, I already did change to \\server\share and this is how it's set up now. But exactly like this, it's not playing on the Asusbox. It did play previously with the mapped drive. Does that make any sense?
im85288 1493 Posted June 26, 2015 Posted June 26, 2015 (edited) It should work the other way around Have you tested playback via the web client to assure your sever paths are set up correctly? You may/may not need to put in smb user/password details depending on how you have things set up. Edited June 26, 2015 by im85288
Kosta 8 Posted June 26, 2015 Author Posted June 26, 2015 (edited) No, but through our talks I found out what the problem is: I was/am using NFS instead of SMB on my Asusbox. SMB access to the NAS is not open without the login and password. So I was actually never been able to access NAS via Samba previously... now I have to figure out the way around this. I reckon the reason why it worked previously with the mapped drive is because the Emby on the Asusbox was browsing through the server, which then apparently automatically "pushed" the file over. Now that I am telling it to pull it from the NAS directly (\\IP-address\share), it cannot, since it has no credentials. NFS needs no credentials, I can simply limit it to the subnet and/or IP(range). I will remove the logs for security reasons. So the question now remains how to solve this, hmm... (and no, there is no uPNP on my network, security reasons and router not supporting it) Edited June 26, 2015 by Kosta
im85288 1493 Posted June 26, 2015 Posted June 26, 2015 I used to use NFS too when I had the server running on a Mac. You need to use path substitution for that. So you can for example map your media drives using the local path like c:/movies then add a path substitution to something like NFS://server/share Does that make sense to you?
Kosta 8 Posted June 26, 2015 Author Posted June 26, 2015 Yes, that makes sense, for that client, because it's the only client using NFS. But, what happens when there's a client not using NFS (for instance, W7pro which has no NFS client)? Then there's a problem...
Kosta 8 Posted June 26, 2015 Author Posted June 26, 2015 Just to update: I found out there is an option called "local master browser" in the Synology, which basically activates Guest account for SMB (no password for SMB shares). It's not something I prefer, but if that's the only option, so be it. It works with that. I will research if there is a chance like in windows to have a credential entered for SMB, but I'm afraid there is not. But I guess it's either that, or I have to make sure I have NFS capability on all clients running KODI (not always possible, as I said, have some clients running W7pro...but if W10pro offers NFS clients, then things might change...). Thanks a lot for the help.
Recommended Posts