View Single Post
Old 11-22-2015, 11:52 AM   #10
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,485
Karma: 8025704
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by Purple Lady View Post
7My settings were set to use the 71 number and I also had checked try suto connect if connection fails in settings. I guess the try auto connect is why the manual connect succeeded. I thought the auto connect would have used the same code as the manual connect and tried auto connect when the IP address specified in settings failed.
Auto-connect does use the same code as manual connect. The two times it failed (20/Nov and 21/Nov at 08:00), your desktop computer failed to answer CC's "is any calibre out there" query. The desktop did answer that query on the 19/Nov auto-connect and on the manual connect on 21/Nov.

What all this says is that something is different at 08:00. I see several possibilities:
  • The desktop computer is off.
  • The desktop computer is asleep. On 19/Nov and before, perhaps it was awakened by some Wake-On-Lan feature that no longer works with the new router.
  • The device is connecting to a different WiFi access point at 08:00 than at 13:25.
  • Calibre isn't running on the desktop computer when CC attempts to connect at 08:00.
Quote:
What I didn't tell you was that after I posted my problem and before I sent the log a I fixed the settings to use the new IP address(68). That's why 68 worked and 71 didn't. The tethering you saw was when I turned off wifi and used LTE on my tablet to make sure that the new IP worked when not connected to home wifi.
I don't see a successful Wireless Device connection to the 68. address except when you were tethered. There is a successful connection to the content server.

In any event you should have had another auto-connect attempt this morning. Did it work?
chaley is offline   Reply With Quote