MobileRead Forums - View Single Post

chaley · 10-08-2017, 11:29 PM

What I understand from what you have told me:

You "used a fixed IP address and port number on my router." I am not sure what this means. The words say that you set up port forwarding on your home network router, but unless you have multiple networks this should have no effect at all. If it does have an effect then your network is partitioned, which is not a CC use case. You might have meant that you "used a fixed IP address and port number on my device", in which case things are clearer.
You have the content server connection working on various ports. This implies that the windows firewall is open for incoming connections on those ports. It isn't clear whether you are using a fixed IP address or CC's auto-connect (Bonjour and broadcast).
The wireless device connection does not work on the same ports. I assume that you ensured that the content server and wireless device never shared the same port. It isn't clear whether you are using a fixed IP address or CC's auto-connect (Bonjour and broadcast).
You obfuscated the IP addresses so I can't tell if they are public or private, although the bits I can see imply you are using a 192.168 private range. FWIW: obfuscating private IP addresses serves no purpose. Everyone in the world uses the same addresses, and if a bad guy gets through your home router's firewall then that bad guy will discover the IP range being used.
You supplied a calibre device detection log. What I asked for was a calibre debug log. A debug log will tell if calibre is able to successfully listen on the specified connection port, indicate whether or not calibre "hears" CC's "are you there" broadcasts, and show if incoming connections arrive but are not serviced by calibre.
You are running McAfee, which is known to cause problems for CC. This is especially true if the installation contains any "spyware" protection, because evidence implied it can do content-based filtering. You say that you disabled McAfee. Our experience is that McAfee can refuse to actually be disabled, leaving parts of itself running even when told not to.

Given all the above, I think the most probable reason for the problem is McAfee. My reasoning: your device can connect to calibre's content server, indicating that there is a network path from CC to calibre. Whatever is preventing the wireless device from working must be interfering with that network path in some way, and by far the most likely candidate is McAfee.

A second possibility is that there is something plugged into the Windows machine that calibre thinks could be a device. Calibre can connect to one device at a time. If you have something plugged in for charging that calibre (partially) recognizes, an active "Connect to Folder", or some other device connection then the wireless device will never connect.

I don't have any further suggestions.

Given that CC doesn't work for you, if you want a refund use the contact form here.

10-08-2017, 11:29 PM	#9
chaley Grand Sorcerer Posts: 12,471 Karma: 8025600 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	What I understand from what you have told me: You "used a fixed IP address and port number on my router." I am not sure what this means. The words say that you set up port forwarding on your home network router, but unless you have multiple networks this should have no effect at all. If it does have an effect then your network is partitioned, which is not a CC use case. You might have meant that you "used a fixed IP address and port number on my device", in which case things are clearer. You have the content server connection working on various ports. This implies that the windows firewall is open for incoming connections on those ports. It isn't clear whether you are using a fixed IP address or CC's auto-connect (Bonjour and broadcast). The wireless device connection does not work on the same ports. I assume that you ensured that the content server and wireless device never shared the same port. It isn't clear whether you are using a fixed IP address or CC's auto-connect (Bonjour and broadcast). You obfuscated the IP addresses so I can't tell if they are public or private, although the bits I can see imply you are using a 192.168 private range. FWIW: obfuscating private IP addresses serves no purpose. Everyone in the world uses the same addresses, and if a bad guy gets through your home router's firewall then that bad guy will discover the IP range being used. You supplied a calibre device detection log. What I asked for was a calibre debug log. A debug log will tell if calibre is able to successfully listen on the specified connection port, indicate whether or not calibre "hears" CC's "are you there" broadcasts, and show if incoming connections arrive but are not serviced by calibre. You are running McAfee, which is known to cause problems for CC. This is especially true if the installation contains any "spyware" protection, because evidence implied it can do content-based filtering. You say that you disabled McAfee. Our experience is that McAfee can refuse to actually be disabled, leaving parts of itself running even when told not to. Given all the above, I think the most probable reason for the problem is McAfee. My reasoning: your device can connect to calibre's content server, indicating that there is a network path from CC to calibre. Whatever is preventing the wireless device from working must be interfering with that network path in some way, and by far the most likely candidate is McAfee. A second possibility is that there is something plugged into the Windows machine that calibre thinks could be a device. Calibre can connect to one device at a time. If you have something plugged in for charging that calibre (partially) recognizes, an active "Connect to Folder", or some other device connection then the wireless device will never connect. I don't have any further suggestions. Given that CC doesn't work for you, if you want a refund use the contact form here.