Quote:
Originally Posted by chaley
There are weird things happening.
|
What's most weird is that it started happening on two different networks at the same time.
Quote:
Originally Posted by chaley
First, there seems to be two calibre machines involved, one whose name starts with a G and one whose name starts with an R. I would guess that the 'G' machine is your home machine.
|
Correct. G is my home machine R is my work machine. Thanks for not shaming me by publicly posting my nerdy machine names.
Quote:
Originally Posted by chaley
There are weird things happening.
The thing that bothers me is that the IP address you manually entered is not the IP address that calibre responds with via automatic connections. Where did you get that IP address? Is it possible that "G" is connected to your network twice?
|
That's the address that shows up in Calibre when I open the connect/share dropdown. It says "Stop Wireless connection [10.0.1.90 or 10.2.1.2 Port 9090]"
Quote:
Originally Posted by chaley
Is it possible that "G" is connected to your network twice?
|
Oops, I had turned on Wifi a couple of days ago when trying to fix the problem. I just turned it off and will send you another debug log.
Quote:
Originally Posted by chaley
Do you have a very congested network?
|
Nope. Its not usually congested, and right now I am the only one doing anything on it.
Quote:
Originally Posted by chaley
A complicated cable/wireless setup?
|
Not really. Desktop with a wired connection to the router. Phone connects wirelessly. Extender in the front of the house that other computers connect to.
Quote:
Originally Posted by chaley
Neighbors who might have wireless hubs that interfere with yours?
|
I guess its possible, but since the started happening at home and at work on the same day, it seems unlikely.
Quote:
Originally Posted by chaley
Clearly something on your network is eating those mDNS packets and, frequently, CC's broadcast packets.
|
This would make more sense if it didn't work if I set the address tom something else and then reset it to the default. Why would that fix it.
Quote:
Originally Posted by chaley
Finally, what happens if you manually enter into CC the IP address 10.0.1.2? Do the failures go away?
|
They do.
So, If I am getting failures with the default settings and change it to 10.0.1.90 it still fails, but if I change it back to the default, then it works.
And, If I I am getting failures with the default settings and change it to 10.0.1.2 it works.
I sent you another debug log.