MobileRead Forums - View Single Post - Can't connect CC to Calibre using Samsung Nook

chaley · 01-15-2018, 05:14 PM

One significant difference: the IP address of the computer running calibre has changed. It was 192.168.1.3, but is now 192.168.1.2. However, the CC debug log shows that *something* answered with 192.168.1.3. That is very strange.

Questions/comments:

Is it possible that calibre is running on more than one computer on the network?
What order did you do the reboots? Best is
1. Turn off all devices
2. Boot router
3. Boot calibre computer
4. Boot Samsung
According to the CC debug log calibre is not answering one of CC's "Are you there" queries. This means that calibre is still being blocked by something.

You could try changing CC's wireless device connection settings to be the default. Unless something changes, such a change won't fix anything because CC is being given the incorrect IP address. One hopes that "something" will change.

Finally, although the "Debug device detection" report is interesting, it isn't the same sort of calibre debug log that you included in the first post. That other debug log is of interest because it indicates whether or not calibre "hears" CC's "are you there" messages.

01-15-2018, 05:14 PM	#4
chaley Grand Sorcerer Posts: 12,449 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	One significant difference: the IP address of the computer running calibre has changed. It was 192.168.1.3, but is now 192.168.1.2. However, the CC debug log shows that something answered with 192.168.1.3. That is very strange. Questions/comments: Is it possible that calibre is running on more than one computer on the network? What order did you do the reboots? Best is Turn off all devices Boot router Boot calibre computer Boot Samsung According to the CC debug log calibre is not answering one of CC's "Are you there" queries. This means that calibre is still being blocked by something. You could try changing CC's wireless device connection settings to be the default. Unless something changes, such a change won't fix anything because CC is being given the incorrect IP address. One hopes that "something" will change. Finally, although the "Debug device detection" report is interesting, it isn't the same sort of calibre debug log that you included in the first post. That other debug log is of interest because it indicates whether or not calibre "hears" CC's "are you there" messages.