Posts: 17
Joined: Jul 2015
Reputation:
0
I had the same issue. I simply changed the port number from the default 80 to 81 - problem solved.
Hope that helps!
Posts: 8
Joined: Oct 2014
Reputation:
0
Hi Kalleanker,
Thanks I tried that but it did not resolve the issue, I also tried using different port numbers with no success.
Cheers
Posts: 70
Joined: May 2014
Reputation:
3
2015-08-16, 13:52
(This post was last modified: 2015-08-16, 14:18 by boris blank.)
Interesting. I wokeup this morning and found that I have exactly the same problem as the OP.
I can access the NAS server that Kodi connects to using the PC through Windows explorer and also the Synology DiskStation web page but Kodi simply cannot see the NAS. Was working perfectly yeaterday when I last used it.
EDIT: Well, i just tried it again and its now working properly. Very odd, especially as I hadn't done anything to try to correct the problem.
Posts: 8
Joined: Oct 2014
Reputation:
0
Hi,
I've my media located on a Netgear ReadyNas, each media type has been set-up as a mapped a drive on my PC e.g. V:\Video etc. and these have been set-up my library sources. I've start-up program on my PC which connects the mapped drives and I've wake on LAN set-up on Kodi to ensure it can connect to the shares on start-up.
The network is just a straight forward Ethernet connection directly to the router which is defined a Private Network by Windows. Both the PC and NAS have been set-up with static IP addresses.
Cheers I'll uninstall Library Auto Updater and will have set the library update on start-up. I use Add-On installer from the TVAddons repository but I can uninstall that and rerun the debug.
If you need further information please let me know. Thanks
Posts: 403
Joined: Mar 2015
Reputation:
3
Have you previuosly had success connecting to your NAS or is this a new setup? (in regards to Kodi)
Posts: 8
Joined: Oct 2014
Reputation:
0
2015-08-17, 10:24
(This post was last modified: 2015-08-19, 21:07 by stigpepper.)
Yes the PC that I've been experiencing the issue with has had Kodi running on it for some time now. I upgraded from win 8.1 to win 10 recently and also upgraded to Isengard around the same time and started to experience the issue.
I can access the media on my NAS but I receive the error message when the library updater runs both when using the out of box updater or the Library Auto Update add on.
I've another PC running win 7 and Isengard and an Android tablet running kodi 14 and have no issues with either of them.
FYI I also tried the following but the error was not resolved: -
Upgraded Kodi from 15 to 15.1
Disabled Windows Firewall
Turned off AVG antivirus
Cheers
Posts: 3
Joined: Oct 2015
Reputation:
0
^ Bump
Hi Guys,
I have the same issue, I have a clean Windows 10 load. I thought it was maybe related to me carrying my Kodi user profile across from previous loads. So i cleared everything of Kodi and did a fresh load, fresh library. I am still having the same issue: If i try to update my movie library "Cannot connect to the remote server".
I have disable my firewall and the issue persists. Kodi states under system info that "internet = Connected".
Any assistance would be greatly appreciated.
Posts: 215
Joined: Sep 2010
Reputation:
5
I had this message pupping up the las two days. The full text goes something like:
Cannot connect to the remote server. Unable to retrieve information about media.
I was able to access my local network content so the actual connection was fine. So the problem had to be connected to the retrieval online information about my content. Because my setup is the way it is, the only info kodi finds itself, is about my music videos. So I disabled scanning of my music videos and the problem disappeared. I guess the audiodb.org has problems for some reason.
Posts: 8
Joined: Oct 2014
Reputation:
0
SOLVED
Yes VortexDK that seems to be the root of the problem alright. I found 2 music video files were causing the issue one had an explanation mark in the title (Dig!) I removed the ! and it was scanned and added to my library. The other file was an .m4v file which was not recognised so I removed it and everything seems to be working perfectly now.