Thanks for the debug log. Unfortunately it doesn't tell me anything other than sometimes it works and sometimes it doesn't. Specifically:
- 11 November: CC connected
- 14 Nov 10:00, CC didn't connect. You made lots and lots of attempts.
- 15 Nov at 14:31 CC didn't connect
- 15 Nov at 14:57 CC connected, without having entered a fixed IP into CC. It worked several more times until
- (all the rest are 15/Nov) 15:08 CC didn't connect
- 15:10 CC connected without a fixed IP
- 15:20:03 CC didn't connect using a fixed IP
- 15:20:45 CC connected with a fixed IP
- and so on
The first thing the above implies is that something between CC and calibre is sometimes blocking network traffic. When CC can connect, CC can also "see" calibre using its detection techniques. When CC cannot connect, none of the detection techniques work either. CC is doing the identical thing each time. Neither the IP address of the device nor the IP address of the calibre machine changed. When CC fails to connect, neither wireless device connections nor content server connections work.
I have no idea what connecting to calibre using a browser would do to make it possible for CC to connect. That said, the fact that it happens on multiple devices points a finger toward the machine running calibre (most probable) or your home network router (not likely but...).
Did anything obvious change between 11/Nov and 14/Nov? You mentioned Norton. Does the problem go away if you turn off Norton's internet security/firewall?
Have you tried rebooting both your devices and the computer running calibre?
My guess is that Norton has added some "heuristic processing" to try to detect bad guys, and that CC's network discovery process is triggering the test. The counter argument is that lots of people run Norton and we aren't hearing complaints.
Sorry I can't be more specific. At least you have a work-around.
