Yes, I know that's localhost - I said localhost right before the address in my post. I thought it was indicating that the Calibre server was somehow interpreting the CC connection as coming from localhost rather than the phone so was replying to the wrong place. However, I've now realised I was misinterpreting the Calibre server access log (as I said, my meds leave my mental processes like they are buried in treacle). The many localhost lines were actually logging my testing the server by connecting to it with my browser on the computer (which works). There are no log lines at all showing access by CC (or FBReader) from the phone. Comodo's View Connections window, however, does show the incoming content server and connect as wireless device connection attempts from the phones - Protocol TCP IN, Source the phone's IP address with port numbers up in the 50000s, destination the laptop's IP address with port numbers 8080 (content server) and 9090 (as wireless device), both as displayed in the Calibre Connect/Share dropdown, Bytes in 148 and 222 bytes, Bytes out 0 bytes.
So CC on the phones (both the new one and the old one that was connecting fine back in early February) are trying to connect, it is getting to my laptop and through Comodo, but Calibre server isn't showing any sign of the access in the logs.
192.168.1.7:33565 is NOT my host machine - it was my old phone's IP address and the port number CC chose to use when I made the last successful connection between CC on the old phone and Calibre back in early February. I was quoting it from the Calibre server access log from Feb 5th to show it was working and connecting then, whereas the only access lines in the log now are from localhost when I test the server from the browser on the laptop.
So - the Calibre server receives and responds to connections from localhost, but doesn't appear to register the connections from the phones, despite the internet Connections Monitor showing they are arriving and being allowed through the firewall. Any ideas anyone?
|