Auto connect problem

[Purple Lady]

My auto connect has failed the past couple of days, but connecting manually works. I have the IP address set to the external one so I can connect outside of the house, but the address changed a few days ago. I have try auto connect if IP address not found checked so I guess that's why connecting manually worked. Let me know if you need me to send a log.

[chaley]

I don't know why it might be failing, so a log might provide some clarity.

Is there anything in the auto-connect log that helps?

[Purple Lady]

The auto connect log says server was found using the old external IP address which doesn't exist anymore. It then says the computer that answered isn't running Calibre. The manual connect looks for another IP if the first isn't found, so I thought that maybe auto connect didn't do that. Hubby is going to ping and see if that IP actually is there somehow.

[Purple Lady]

Hubby just did a ping, and the IP address does not exist. I'll send the debug log.

[theducks]

Originally Posted by Purple Lady

Hubby just did a ping, and the IP address does not exist. I'll send the debug log.

Your firewall may have blocked the sstem or the IP of the host also changed. I set my route to always assign the same IP to systems that act as some kind of 'host' (this also makes it easy to take a Laptop off site and return and get a 'standard' IP) I have a 'connected' home. I can peak out with 32 IP's active (almost all are used as wired)

[Purple Lady]

Originally Posted by theducks

Your firewall may have blocked the sstem or the IP of the host also changed. I set my route to always assign the same IP to systems that act as some kind of 'host' (this also makes it easy to take a Laptop off site and return and get a 'standard' IP) I have a 'connected' home. I can peak out with 32 IP's active (almost all are used as wired)

I did say in the first post that the IP address changed for external access. New router and software changed it. I'll see if hubby can do something so it doesn't change.

[theducks]

Originally Posted by Purple Lady

I did say in the first post that the IP address changed for external access. New router and software changed it. I'll see if hubby can do something so it doesn't change.

I was talking about the Inside IP that the router port forwards to.
The WAN side typically changes unless your ISP offers a Static IP. The biggies charge extra. I was lucky, when I switched, my sales contact said "do you want a static IP?" Me: what does it cost? "Nothing" Me:YES!

If yoy don't have that option, you need to set up (or reconfigure the router) to use a dynamic forwarding service like DynDNS (you may have had one set on your old router)

[chaley]

Originally Posted by Purple Lady

Hubby just did a ping, and the IP address does not exist. I'll send the debug log.

I can tell you what is happening, but I can't say why.

It seems that your auto-connect time is 08:00.

On 19/Nov your device woke up. CC saw that you have programmed an IP/port of 71.???.???.47 port 8012. It also saw that you have checked the "Try automatic" box. CC did a "broadcast" (tried to find any calibre instances) and found one on Hom... at 192.168.?.?9 port 8012. CC then tried to connect to the 71 address. This connect failed, so CC fell back to the 192 address. This succeeded.

On 20/Nov CC woke up and saw the same programmed IP address (71 ...). However, this time no computer answered the broadcast so CC had no fall back address. The connection to 71 ... failed. I don't know why Hom... didn't answer this time.

The same thing happened on 21/Nov at 08:00. Hom... didn't answer the broadcast so no fallback was available.

However, on 21/Nov at 13:25, CC attempted to connect, triggered manually. This time things went as on 19/Nov: the 71 address didn't work but Hom... answered the broadcast with the same IP address as on 19/Nov. The connect succeeded.

Strangely, on 21/Nov at 13:37 CC attempted to connect again, but this time apparently tethering is turned on. The device was acting as an access point. This time CC used a different user-specified IP address: 68.???.???.166. The connection succeeded.

So, what we know is that:

• the 71... address never succeeds
• Hom... has stopped answering broadcasts at 08:00 but answered one later in the day.
• the address 68... worked once while your device was acting as a portable hotspot.

A guess: Hom... is asleep at 08:00? Or calibre is not running?

[Purple Lady]

Originally Posted by chaley

I can tell you what is happening, but I can't say why.

It seems that your auto-connect time is 08:00.

On 19/Nov your device woke up. CC saw that you have programmed an IP/port of 71.???.???.47 port 8012. It also saw that you have checked the "Try automatic" box. CC did a "broadcast" (tried to find any calibre instances) and found one on Hom... at 192.168.?.?9 port 8012. CC then tried to connect to the 71 address. This connect failed, so CC fell back to the 192 address. This succeeded.

On 20/Nov CC woke up and saw the same programmed IP address (71 ...). However, this time no computer answered the broadcast so CC had no fall back address. The connection to 71 ... failed. I don't know why Hom... didn't answer this time.

The same thing happened on 21/Nov at 08:00. Hom... didn't answer the broadcast so no fallback was available.

However, on 21/Nov at 13:25, CC attempted to connect, triggered manually. This time things went as on 19/Nov: the 71 address didn't work but Hom... answered the broadcast with the same IP address as on 19/Nov. The connect succeeded.

Strangely, on 21/Nov at 13:37 CC attempted to connect again, but this time apparently tethering is turned on. The device was acting as an access point. This time CC used a different user-specified IP address: 68.???.???.166. The connection succeeded.

So, what we know is that:

• the 71... address never succeeds
• Hom... has stopped answering broadcasts at 08:00 but answered one later in the day.
• the address 68... worked once while your device was acting as a portable hotspot.

A guess: Hom... is asleep at 08:00? Or calibre is not running?

71 doesn't succeed because it no longer exists. I guess I wasn't clear what the problem was. New router and software changed the outside IP address from 71 to 68. My 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.

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.

[chaley]

Originally Posted by Purple Lady

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.

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?

[Purple Lady]

Yes, the auto connect worked this morning.

[chaley]

Originally Posted by Purple Lady

Yes, the auto connect worked this morning.

[Purple Lady]

Hubby was on the computer this morning and possibly was yesterday. Tomorrow he will be at work so the computer should be asleep so I can see if it's a problem then. Thanks for the help and sorry for the confusion.

[Purple Lady]

I was looking at the auto connect log and noticed a difference on the days it didn't work. The days it did work showed Found fixed IP with auto-connect fallback, and the days that it didn't connect don't show that text. I changed to the proper IP address after the auto connect on 11-21.


08:00:00: ****** Starting connection on 2015-11-19
08:00:08: Found fixed IP with auto-connect fallback: 71... , 192...

08:00:00: ****** Starting connection on 2015-11-20
08:00:13: Server found: 71...
08:00:13: The computer that answered does not seem to be running calibre

08:00:21: ****** Starting connection on 2015-11-21
08:00:24: Server found: 71...
08:00:29: The computer that answered does not seem to be running calibre

08:00:01: ****** Starting connection on 2015-11-22
08:00:22: Found fixed IP with auto-connect fallback: 68... , 192...

[chaley]

Originally Posted by Purple Lady

I was looking at the auto connect log and noticed a difference on the days it didn't work. The days it did work showed Found fixed IP with auto-connect fallback, and the days that it didn't connect don't show that text. I changed to the proper IP address after the auto connect on 11-21.


08:00:00: ****** Starting connection on 2015-11-19
08:00:08: Found fixed IP with auto-connect fallback: 71... , 192...

08:00:00: ****** Starting connection on 2015-11-20
08:00:13: Server found: 71...
08:00:13: The computer that answered does not seem to be running calibre

08:00:21: ****** Starting connection on 2015-11-21
08:00:24: Server found: 71...
08:00:29: The computer that answered does not seem to be running calibre

08:00:01: ****** Starting connection on 2015-11-22
08:00:22: Found fixed IP with auto-connect fallback: 68... , 192...

The messages in the auto-connect log aren't right. When CC says "server found" CC really means that it is going to try that IP manually specified address. When CC says "The computer that answered ..." CC really means "No computer answered". I will fix both of these messages.

Taking into consideration the above confusion and the message changes I am making, what the log should really be saying is

08:00:00:  ****** Starting connection on 2015-11-19
08:00:08:  Found fixed IP with auto-connect fallback: 71... , 192... 

08:00:00:  ****** Starting connection on 2015-11-20
08:00:13:  Server to check: 71... 
08:00:13:  Could not find a computer running calibre

08:00:21:  ****** Starting connection on 2015-11-21
08:00:24:  Server to check: 71... 
08:00:29:  Could not find a computer running calibre

08:00:01:  ****** Starting connection on 2015-11-22
08:00:22:  Found fixed IP with auto-connect fallback: 68... , 192...

The fact that the last one says "with auto-connect fallback" tells us that calibre was alive and running on a machine on the local WiFi network and responded to CC's "are there any calibre instances out there" message. I can't tell from this log whether the 68... address worked, but it is certain that the 192... address would work.