Windows 10 - All clients except localhost cannot tune

[liamnewman]

Hi,
I have recently upgraded from windows 7 to windows 10. On windows 7, all the clients responded fine, and could tune into the server. However, once I upgraded, I started to have issues regarding the clients. While tuning on the main server worked fine, all the clients that used a hostname or ip address were unable to tune, citing a "buffering 0%" message on the Kodi client. I am considering compiling from source to see if that fixes the issues, but as of right now, I am running 2.3 stable. I'm hoping someone can help me with this issue, as otherwise I will have to downgrade back to my last stable configuration on windows 7.

Thanks!

[Ostrich]

hi,
try to use an advancedsettings.xml with this Content:

<pvr>
<minvideocachelevel>20</minvideocachelevel>
<minaudiocachelevel>20</minaudiocachelevel>
</pvr>

http://forum.kodi.tv/showthread.php?tid=159142

it was useful for me!

[luetty]

Do you have upgraded the tv-server (from any to win10) too?

I know a 0% buffering issue, normaly on Linux/ Android Clients.
Please give a try to the following:
- call filemanager (not video/ Picture - just filemanager) within Kodi
- connect to your tv-server with your credentials
- save the credentials there for future use
Try again to tune a channel.

[logifuse]

With Linux clients, the filemanager entry also needs to match the case of the share. e.g. in the Recorder console, if your timeshift is shared as \\Server\Timeshift, the entry in file manager needs to have the capital 'S' in Server & capital 'T' in Timeshift, not lower case.

Back to the OP - it sounds like Windows 10 doesn't have network discovery & file sharing enabled.

[Infidelus]

Back to the OP - it sounds like Windows 10 doesn't have network discovery & file sharing enabled.

That wouldn't surprise me. I've installed a bunch of machines with Windows 10, and they do seem to default to a Public Network. You need to change a setting in Homegroups to make it a Private network, or manually set discovery & sharing for public.

[liamnewman]

Hi,
I am currently downgraded back to 7, but it seems like there is plenty of solutions for me to try. I'll have to upgrade back to 10, and give details on what works.

Thanks

[liamnewman]

Do you have upgraded the tv-server (from any to win10) too?

Argus is installed on the TV Server. The clients are also windows-based. Upgrading a client to 10 yielded the same issue.

[liamnewman]

Thanks for the help!

Turns out that Windows 10 enabled a setting enabling password protection, which caused my clients to be unable to connect (even though they were able to connect to the server)

Disabling it solved the issue. Once again, thanks!