MobileRead Forums - View Single Post

chaley · 10-04-2016, 04:33 AM

Thanks for the debug logs. What they show is that CC can "see" the computer running calibre, can send a message to calibre on that computer, and that calibre can respond. Up to 17 Sept, CC could connect. After 17/Sept connections failed. CC gets a response from calibre when "broadcasting" to find calibre's IP address, but CC fails to connect to either the wireless device port (9090) or the content server port (8080).

The fact that CC gets a response when "broadcasting" means that the router is not the problem, unless the router is set up to block connections on well-known ports. I don't know of any routers that do that, but that doesn't mean there isn't one. What is the brand and model of your router?

The problem is almost certainly caused by "security SW" on the computer running calibre. Something is blocking calibre from accepting network connections on ports 8080 or 9090. The security SW could be a firewall, an antivirus, or a network "security suite" like McAfee, Norton, Bitdefender, MalwareBytes, etc. You need to determine how to tell this SW that calibre is allowed to accept network connections. You can test if security SW is the problem by starting your machine in Safe Mode as described in section 7 of our How To Connect FAQ.

One interesting thing: when connections worked your device had the IP address 192.168.2.5. On or around 17 September that address changed to 192.168.2.4, after which connections stopped working. Is it possible that at some point you told the security SW on the machine running calibre to allow the 2.5 address?

One experiment you could run is to tell your router to give the 2.5 address to your device. You would do this in DHCP settings. Doing this can be complicated and fiddly, so don't do it if you aren't clear on how to go about it.

10-04-2016, 04:33 AM	#3
chaley Grand Sorcerer Posts: 12,449 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	Thanks for the debug logs. What they show is that CC can "see" the computer running calibre, can send a message to calibre on that computer, and that calibre can respond. Up to 17 Sept, CC could connect. After 17/Sept connections failed. CC gets a response from calibre when "broadcasting" to find calibre's IP address, but CC fails to connect to either the wireless device port (9090) or the content server port (8080). The fact that CC gets a response when "broadcasting" means that the router is not the problem, unless the router is set up to block connections on well-known ports. I don't know of any routers that do that, but that doesn't mean there isn't one. What is the brand and model of your router? The problem is almost certainly caused by "security SW" on the computer running calibre. Something is blocking calibre from accepting network connections on ports 8080 or 9090. The security SW could be a firewall, an antivirus, or a network "security suite" like McAfee, Norton, Bitdefender, MalwareBytes, etc. You need to determine how to tell this SW that calibre is allowed to accept network connections. You can test if security SW is the problem by starting your machine in Safe Mode as described in section 7 of our How To Connect FAQ. One interesting thing: when connections worked your device had the IP address 192.168.2.5. On or around 17 September that address changed to 192.168.2.4, after which connections stopped working. Is it possible that at some point you told the security SW on the machine running calibre to allow the 2.5 address? One experiment you could run is to tell your router to give the 2.5 address to your device. You would do this in DHCP settings. Doing this can be complicated and fiddly, so don't do it if you aren't clear on how to go about it.