Quote:
Originally Posted by any_holder
SMART_DEV ( 0.01: 0.005) _attach_to_port try ip address "" on port 9090
SMART_DEV ( 0.99: 0.838) _startup_on_demand listening on port 9090
SMART_DEV ( 1.08: 0.001) _attach_to_port try ip address "" on port 54982
SMART_DEV ( 1.12: 0.000) _startup_on_demand broadcast socket listening on port 54982
SMART_DEV ( 2.23: 1.070) run All IP addresses {'{CDEE4198-D073-4268-8C7F-CCE749E0001E}': [{'netmask': u'255.255.255.255', 'broadcast': u'192.168.1.5', 'addr': u'192.168.1.5'}], '{B1F338BC-E959-11E7-AD35-806E6F6E6963}': [{'netmask': u'255.255.255.255', 'broadcast': u'127.0.0.1', 'addr': u'127.0.0.1'}]}
|
The calibre debug log says that something on the Win10 machine is blocking incoming packets to calibre. If calibre were able to receive packets then you would see lines like the following. The first is CC asking calibre what IP and port to use, the second is the actual connection.
Code:
SMART_DEV ( 117.06:115.091) run received broadcast ('localhost', ('192.168.120.7', 54982)) calibre wireless device client (on wallaby);8080,9090
SMART_DEV ( 120.07: 3.003) run attempt to open device socket
The fact that pings work indicate that the blockage is further up in the system. My guess is that the firewall is not in fact neutralized, or that some other McAfee component is blocking incoming packets.