Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Software > Calibre Companion

Notices

Reply
 
Thread Tools Search this Thread
Old 01-15-2018, 01:51 PM   #1
pmatch1104
Enthusiast
pmatch1104 began at the beginning.
 
Posts: 31
Karma: 10
Join Date: Dec 2010
Device: Nook
Can't connect CC to Calibre using Samsung Nook

In the past, I've been able to connect my CC app on my Samsung Nook to calibre via the wireless connection ... but it has been about a year since the last time I did. I've updated my calibre app on my laptop, made sure my CC app on my tablet is up to date, made sure my firewall is allowing "the main calibre program" through, and made sure both are using the same band on my WiFi. But I keep getting the "failed to connect" error message regarding the IP address. I've read through the Help instructions and nothing seems to fix the problem.

I'm not a very techy person but can follow detailed instructions. I remember having this same problem in the past, but not how I got it fixed. Any help you can give me will be greatly appreciated! Thanks.

calibre Debug log
calibre 3.15 embedded-python: True is64bit: False
Windows-10-10.0.16299-SP0 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '10', '10.0.16299')
Python 2.7.12+
Windows: ('10', '10.0.16299', 'SP0', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeDRM (6, 5, 3) && Generate Cover (1, 5, 21)
calibre 3.15 embedded-python: True is64bit: False
Windows-10-10.0.16299-SP0 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '10', '10.0.16299')
Python 2.7.12+
Windows: ('10', '10.0.16299', 'SP0', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeDRM (6, 5, 3) && Generate Cover (1, 5, 21)
Turning on automatic hidpi scaling
devicePixelRatio: 1.0
logicalDpi: 120.0 x 120.0
physicalDpi: 127.664921466 x 127.590697674
Using calibre Qt style: True
Starting up...
SMART_DEV ( 0.01: 0.010) _attach_to_port try ip address "" on port 9090
SMART_DEV ( 0.94: 0.803) _startup_on_demand listening on port 9090
SMART_DEV ( 1.03: 0.001) _attach_to_port try ip address "" on port 54982
SMART_DEV ( 1.07: 0.000) _startup_on_demand broadcast socket listening on port 54982
SMART_DEV ( 2.13: 1.027) run All IP addresses {'{D859C08B-CA32-11E7-9D36-806E6F6E6963}': [{'broadcast': u'127.0.0.1', 'netmask': u'255.255.255.255', 'addr': u'127.0.0.1'}], '{BE0BFF1F-4C19-45EF-A717-20C735D998E2}': [{'broadcast': u'192.168.1.3', 'netmask': u'255.255.255.255', 'addr': u'192.168.1.3'}]}
Started up in 18.42 seconds with 2001 books
SMART_DEV ( 0.00: 0.002) _attach_to_port try ip address "" on port 9090
SMART_DEV ( 0.85: 0.818) _startup_on_demand listening on port 9090
SMART_DEV ( 0.91: 0.000) _attach_to_port try ip address "" on port 54982
SMART_DEV ( 0.94: 0.000) _startup_on_demand broadcast socket listening on port 54982
SMART_DEV ( 2.01: 1.037) run All IP addresses {'{D859C08B-CA32-11E7-9D36-806E6F6E6963}': [{'broadcast': u'127.0.0.1', 'netmask': u'255.255.255.255', 'addr': u'127.0.0.1'}], '{BE0BFF1F-4C19-45EF-A717-20C735D998E2}': [{'broadcast': u'192.168.1.3', 'netmask': u'255.255.255.255', 'addr': u'192.168.1.3'}]}
Attached Files
File Type: txt calibre.companion.debug.log.txt (350.9 KB, 220 views)

Last edited by pmatch1104; 01-15-2018 at 02:06 PM. Reason: Adding calibre debug log
pmatch1104 is offline   Reply With Quote
Old 01-15-2018, 03:00 PM   #2
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,734
Karma: 6690881
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
I responded to your email with this:
Quote:
The debug log indicates that the computer running calibre is not allowing connections from CC to calibre. The usual reasons for this are:
  • The antivirus (AV) SW on the calibre machine (vast majority of cases)
  • The firewall on the calibre computer is blocking CC (most of cases that are left)
  • (Windows) The "network connection" is not set to "Private" (somewhat rare)
  • The home WiFi router is set to block connections (rare)
  • The home WiFi router needs to be rebooted (rare).
The debug log also says that the computer running calibre can respond to some of CC's "Are you there" requests but not connection requests. This implies (a lot) that the problem is the AV or the firewall. Without physical access to your network I can't say much more.

FWIW: windows and AV updates happen all the time, usually without telling you. Any update can break networking.

My first suggestion: reboot everything (the WiFi router, the Samsung device, and the computer running calibre in that order) and see if the problem goes away. My guess is that it won't. The next suggestion: do whatever you must do to add calibre as an exception to your AV and firewall. It might help to remove any existing exceptions before adding new ones.
chaley is offline   Reply With Quote
Old 01-15-2018, 04:52 PM   #3
pmatch1104
Enthusiast
pmatch1104 began at the beginning.
 
Posts: 31
Karma: 10
Join Date: Dec 2010
Device: Nook
No luck ... I rebooted the modem, the router, allowed access to AV and firewall with no results. I reran the debug reports. Do you see anything different?

calibre 3.15 embedded-python: True is64bit: False
Windows-10-10.0.16299 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '10', '10.0.16299')
Python 2.7.12+
Windows: ('10', '10.0.16299', '', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeDRM (6, 5, 3) && Generate Cover (1, 5, 21)
USB devices on system:
(USBDevice(vendor_id=0x4f2 product_id=0xb40e bcd=0x6939 devid=usb\vid_04f2&pid_b40e&rev_6939 devinst=1),
USBDevice(vendor_id=0x2687 product_id=0xfb01 bcd=0x100 devid=usb\vid_2687&pid_fb01&rev_0100&mi_00 devinst=2),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1203 devid=usb\vid_046d&pid_c52b&rev_1203&mi_01 devinst=3),
USBDevice(vendor_id=0x2687 product_id=0xfb01 bcd=0x100 devid=usb\vid_2687&pid_fb01&rev_0100&mi_01 devinst=4),
USBDevice(vendor_id=0x8087 product_id=0x8000 bcd=0x4 devid=usb\vid_8087&pid_8000&rev_0004 devinst=5),
USBDevice(vendor_id=0x4f2 product_id=0xb40e bcd=0x6939 devid=usb\vid_04f2&pid_b40e&rev_6939&mi_00 devinst=6),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1203 devid=usb\vid_046d&pid_c52b&rev_1203&mi_02 devinst=7),
USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub20&vid8086&pid9c26&rev0004 devinst=8),
USBDevice(vendor_id=0x8087 product_id=0x7dc bcd=0x1 devid=usb\vid_8087&pid_07dc&rev_0001 devinst=9),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1203 devid=usb\vid_046d&pid_c52b&rev_1203 devinst=10),
USBDevice(vendor_id=0x4f3 product_id=0x36c bcd=0x1112 devid=usb\vid_04f3&pid_036c&rev_1112 devinst=11),
USBDevice(vendor_id=0x2687 product_id=0xfb01 bcd=0x100 devid=usb\vid_2687&pid_fb01&rev_0100 devinst=12),
USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid8086&pid9c31&rev0004 devinst=13),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1203 devid=usb\vid_046d&pid_c52b&rev_1203&mi_00 devinst=14))

No disabled plugins
Looking for devices of type: MTP_DEVICE
The Windows WPD service says there are no portable devices connected

Looking for devices of type: SMART_DEVICE_APP
All IP addresses {'{BE0BFF1F-4C19-45EF-A717-20C735D998E2}': [{'netmask': u'255.255.255.255', 'addr': u'192.168.1.2', 'broadcast': u'192.168.1.2'}], '{D859C08B-CA32-11E7-9D36-806E6F6E6963}': [{'netmask': u'255.255.255.255', 'addr': u'127.0.0.1', 'broadcast': u'127.0.0.1'}]}
No device is connected

Looking for devices...

Devices possibly connected: None
Attached Files
File Type: txt calibre.companion.debug.log2.txt (382.8 KB, 190 views)
pmatch1104 is offline   Reply With Quote
Old 01-15-2018, 05:14 PM   #4
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,734
Karma: 6690881
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
One significant difference: the IP address of the computer running calibre has changed. It was 192.168.1.3, but is now 192.168.1.2. However, the CC debug log shows that *something* answered with 192.168.1.3. That is very strange.

Questions/comments:
  • Is it possible that calibre is running on more than one computer on the network?
  • What order did you do the reboots? Best is
    1. Turn off all devices
    2. Boot router
    3. Boot calibre computer
    4. Boot Samsung
  • According to the CC debug log calibre is not answering one of CC's "Are you there" queries. This means that calibre is still being blocked by something.
You could try changing CC's wireless device connection settings to be the default. Unless something changes, such a change won't fix anything because CC is being given the incorrect IP address. One hopes that "something" will change.

Finally, although the "Debug device detection" report is interesting, it isn't the same sort of calibre debug log that you included in the first post. That other debug log is of interest because it indicates whether or not calibre "hears" CC's "are you there" messages.
chaley is offline   Reply With Quote
Old 01-15-2018, 07:39 PM   #5
pmatch1104
Enthusiast
pmatch1104 began at the beginning.
 
Posts: 31
Karma: 10
Join Date: Dec 2010
Device: Nook
Hello again ... and thank you for your patience and help.

I tried all of the steps above and still get the same results.

calibre Debug log
calibre 3.15 embedded-python: True is64bit: False
Windows-10-10.0.16299 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '10', '10.0.16299')
Python 2.7.12+
Windows: ('10', '10.0.16299', '', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeDRM (6, 5, 3) && Generate Cover (1, 5, 21)
calibre 3.15 embedded-python: True is64bit: False
Windows-10-10.0.16299 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '10', '10.0.16299')
Python 2.7.12+
Windows: ('10', '10.0.16299', '', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeDRM (6, 5, 3) && Generate Cover (1, 5, 21)
Turning on automatic hidpi scaling
devicePixelRatio: 1.0
logicalDpi: 120.0 x 120.0
physicalDpi: 127.664921466 x 127.590697674
Using calibre Qt style: True
Starting up...
SMART_DEV ( 0.00: 0.003) _attach_to_port try ip address "" on port 9091
SMART_DEV ( 0.91: 0.805) _startup_on_demand listening on port 9091
SMART_DEV ( 0.97: 0.001) _attach_to_port try ip address "" on port 54982
SMART_DEV ( 1.01: 0.000) _startup_on_demand broadcast socket listening on port 54982
SMART_DEV ( 2.09: 1.042) run All IP addresses {'{BE0BFF1F-4C19-45EF-A717-20C735D998E2}': [{'netmask': u'255.255.255.255', 'addr': u'192.168.1.4', 'broadcast': u'192.168.1.4'}], '{D859C08B-CA32-11E7-9D36-806E6F6E6963}': [{'netmask': u'255.255.255.255', 'addr': u'127.0.0.1', 'broadcast': u'127.0.0.1'}]}
Started up in 17.11 seconds with 2001 books
SMART_DEV ( 0.00: 0.002) _attach_to_port try ip address "" on port 9090
SMART_DEV ( 0.86: 0.820) _startup_on_demand listening on port 9090
SMART_DEV ( 0.92: 0.000) _attach_to_port try ip address "" on port 54982
SMART_DEV ( 0.95: 0.000) _startup_on_demand broadcast socket listening on port 54982
SMART_DEV ( 2.03: 1.050) run All IP addresses {'{BE0BFF1F-4C19-45EF-A717-20C735D998E2}': [{'netmask': u'255.255.255.255', 'addr': u'192.168.1.4', 'broadcast': u'192.168.1.4'}], '{D859C08B-CA32-11E7-9D36-806E6F6E6963}': [{'netmask': u'255.255.255.255', 'addr': u'127.0.0.1', 'broadcast': u'127.0.0.1'}]}

I sent the debug log from CC to the email address. I noticed that the number changed after rebooting everything. Any other suggestions?
pmatch1104 is offline   Reply With Quote
Old 01-15-2018, 08:56 PM   #6
pmatch1104
Enthusiast
pmatch1104 began at the beginning.
 
Posts: 31
Karma: 10
Join Date: Dec 2010
Device: Nook
Hallelujah!!! I got it fixed. The problem was my firewall network somehow got set to Public instead of Private. Once I changed it back to Private, the connection went through. Thanks for all your help.
pmatch1104 is offline   Reply With Quote
Old 01-16-2018, 04:42 AM   #7
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,734
Karma: 6690881
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by pmatch1104 View Post
Hallelujah!!! I got it fixed. The problem was my firewall network somehow got set to Public instead of Private. Once I changed it back to Private, the connection went through. Thanks for all your help.
Excellent! And you are welcome.
chaley is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Calibre stopped recognizing my Nook Samsung Galaxy S2 kathybaug Devices 3 12-09-2016 09:18 PM
Samsung galaxy tab e nook and calibre rjherald Devices 1 12-04-2016 08:52 PM
Calibre & Samsung Nook Tab E tracings Barnes & Noble NOOK 0 02-18-2016 09:54 PM
Calibre 2.0 Samsung Galaxy Tab 4 Nook MGlitch Devices 13 09-07-2014 02:21 AM
connect to calibre wirelessly with my nook? davea0511 General Discussions 1 01-03-2011 09:57 AM


All times are GMT -4. The time now is 11:02 AM.


MobileRead.com is a privately owned, operated and funded community.