Cannot play from client machines

[Adiventure 2]

It was suggested I start a new thread and so I do.

 

Started a server on a windows machine, can view files locally and via the webportal but not through the emby for kodi addon on other machines in my local network.

 

When trying to play file the error pops "the file is no longer available". When scanning files I get the error 'files can't be located, check network credentials or use path substitution'.

 

In library the folders are labled using their smb share address only.

 

On the clients I have tried http and direct play, and addon and native.

 

For network credentials I have been using servername, servername\windowslogin, windowspassword obviously using the account that setup the shares and has access. I have for the sake of thoroughness tried the ip instead of servername, \\servername, and using the username without there servername\ piece.

 

 

 

Most recent client log:

http://paste.ubuntu.com/23779002/

Much longer client log:

http://paste.ubuntu.com/23778202/

I have attached 2 server logs too, the most recent of which I believe is the most useful.

Log 2.txt

Log 1.txt

[Adiventure 2]

you need to do a DB reset if you change this, did you?

 

Have you tried HTTP direct Streaming, turn on Addon Playback, reset DB and make sure play via HTTP is set in the addon settings.

 

Try using the file browser in Kod to browse to the share where your media is stored, can you play media by navigating to it using the file browser and selecting your media manually.

I did not know DB resets were required, but had done some intermittently. Trying the steps you listed did not work. I have tried changing the SMB shares from hidden to visible (Movies$ to Movies) and am currently doing a library rescan so I don't know if it is working from the file browser within Kodi. It does work from an external file manager app however.

[Adiventure 2]

Thanks for the effort. Could you confirm the proper syntax for the network credentials? As I mentioned I've tried all the combinations, but it'd rule out a failure point if I knew for sure it was right every time. Would it also be useful for me to post more detailed logs?

Edited January 11, 2017 by Adiventure

[im85288 1493]

The logs supplied are not really any use, did you follow the link I gave you on how to create and report? I looked at both your client logs (we have no interest in your server logs) and none of them contained an error on playback.

 

What we need to see is the error in your logs on playback (remember I said you could skip the warning message so the logs at scanning time of your library are not needed).

 

Another guess from me is it may be permissions, since your using Linux try the NFS protocol (which does not need permissions and performs better than SMB anyway)

[Adiventure 2]

I can't figure what is/was going on.

 

Currently things seem to be working normally, for the first time. The only difference I can isolate besides many reinstall of every component is that the server is sharing as visible smb shares instead of invisible. I don't however see how that would actually change anything.

 

 

The logs I sent were produced exactly as you requested. The reason for the overlap with scanning is because it has been pretty consistently scanty seemingly in indefinitely on boot up. As best as I could tell reading through no error was written to the logs when I attempted playback.

 

While I have a few Android clients, both the server and most used other machine are windows. Is there a better protocol that would be compatible all around?

 

Also could you possibly confirm the syntax required for network credentials? I gather I have it right currently, but I'd like to avoid stressing should I ever need to reenter it.

[Adiventure 2]

Heh,at times sure, but I promise I also did the change one thing and test it system. It will prompt entering credentials,at least once, I'm just not 100% sure which one did it.