Quote:
Originally Posted by tamhas
Here's the Calibre log. This time I got a popup from Windows Firewall asking if I want to allow it. I did, but no change in the result.
|
Did you attempt to connect while calibre was in "debug log" mode? If you did then calibre did not receive the packets.
I say again that the CC debug log showed that CC could "see" the calibre computer. The two debug logs say that CC cannot see the calibre program. Something on the desktop is stopping it. I can't say what. FWIW: I have zero confidence in "turning off" AV programs. Countless times we have seen disabled AV programs still running. The best method we know of is to boot in safe mode.
One thing to check: is the network marked as "Private"? If not then CC will not be allowed to connect.
Another thing to check: is the firewall set to allow calibre access?
A third thing to check is to verify that I am not smoking something when I say that the device can "see" the calibre computer. Start the content server in calibre, then on the device start a browser and enter
Code:
http://ip address:CS port/
You should see something like the following.
Of course the AV/firewall could block this as well. Another connectivity check is to install a network utility that contains a "PING" function and then see if the device can ping the calibre computer. I have used
Ping and DNS to do this, but there are a zillion other choices. You can also do the connectivity check from the calibre computer by opening a CMD window and typing
Code:
ping ip-address-of-device
It is getting very close to the point where the only thing I can do is offer you a refund. I simply cannot debug the networking on your desktop computer.