Kodi Community Forum

Full Version: Connection issues - probably IPv6 related?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

Just this weekend, I updated my HTPC to Windows 8 Pro. I hoped that would be as painless as when I updated my other PC's - but no Sad
My HTPC is running several "web-servers" - CouchPotato, Sickbeard, etc.. But it's also running a Node.js-server, which is acting as a proxy to all these other web interfaces - and this proxy is set up for port 80.
Now, when using Windows 8, the system automatically occupies port 80 for something called "http.sys" (See http://www.mikeplate.com/2011/11/06/stop...n-windows/ for more detail) - this is for .Net-apps (and others) to have a common API for serving up things.
This meant, that I could not use my Node.js-based proxy. But the above link had a solution! Just make http.sys use IPv6, and leave port 80 free on IPv4!
But now XBMC cannot connect to the Argus TV Core anymore! Here's a log of the error:

17:29:32 T:5180   ERROR: AddOnLog: ARGUS TV client: can not write to http://localhost:49943/ArgusTV/Core/Ping/52
17:29:32 T:5180   ERROR: AddOnLog: ARGUS TV client: Ping failed... No connection to Argus TV.
17:29:33 T:5180   ERROR: ADDON: Dll ARGUS TV client - Client returned bad status (6) from Create and is not usable
17:29:33 T:5180 WARNING: PVR::CPVRClients::UpdateAndInitialiseClients - failed to create add-on ARGUS TV client, status = 6
17:29:33 T:5180 WARNING: PVR::CPVRClients::UpdateAndInitialiseClients - failed to load the dll for add-on ARGUS TV client, disabling it
17:29:33 T:3920  NOTICE: Thread CAddonStatusHandler:pvr.argustv start, auto delete: true

Does this mean anything to anyone?? Smile Using both and localhost do not work. I changed it to localhost, because it was mentioned in the article above.

Thanks in advance!
If anyone runs into this issue in the future, I found a solution here:

Stop the service "World Wide Web Publishing Service", and set startup to manual.
The thing with diverting the http.sys module to use IPv6 does not work, as some part of the Argus-XBMC plugin apparently needs IPv4