CC unable to connect to Calibre

[deraeler]

Through EXTENSIVE reading, testing, reconfiguring....I've determined that CC v5.3.2.4 on Android/Samsung S7 can only connect to my Calibre server running on a Windows 10 HP laptop, when I'm using my unsecured Wireless-G network. If I switch to my secured wireless-N network, it will not connect, no matter how I reconfigure things, and this is with Firewall/AV/AntiMalware all disabled.

Why is this?

Nevermind using newer network protocols, Wireless-N is 5-yr old technology and it won't work...which tells me I'm in for another nightmare when I upgrade my router.

I've enabled Mixed mode on my router's N config...makes no difference.

IP/Port reconfig etc etc etc etc makes no difference.

Any insights appreciated.

[davidfor]

Does Windows see the device when you can connect via the Wireless-N network? If so, is it seeing the device in a different way to when connected via wireless-G?

Calibre is using the OS to connect to any device. Calibre needs the OS to be able to see the device and present it in an expected way. If the OS doesn't see it, calibre can't. Check if you can access the device from Windows, and if you can run the steps in My device is not detected by calibre. Then, connect via Wireless-G, disable the driver being used by calibre, and run the last step again. The difference in what the OS is reporting to calibre for the two connection methods is probably the important thing here.

[DoctorOhh]

Moderator Notice
Moved thread to the Calibre Companion forum.

[chaley]

Originally Posted by deraeler

Through EXTENSIVE reading, testing, reconfiguring....I've determined that CC v5.3.2.4 on Android/Samsung S7 can only connect to my Calibre server running on a Windows 10 HP laptop, when I'm using my unsecured Wireless-G network. If I switch to my secured wireless-N network, it will not connect, no matter how I reconfigure things, and this is with Firewall/AV/AntiMalware all disabled.

Why is this?

My guess is that the "secured" network is enforcing guest mode, wireless isolation, or SSID isolation. It also might be refusing to pass packets between bands or to the cabled network. It also might has some kind of IP-level access control.

I can guarantee you that neither CC nor calibre care what WiFi protocol or band is being used.

[deraeler]

Well I just lost everything I'd been typing here for the last 20 minutes, so forgive the abbreviated response.

Nothing above is relevant. I've re-enabled my antivirus anti malware firewall etc. Makes no difference.

G works, N doesnt.
Not sure what you mean by "see my device", I'm only connecting to Calibre on my laptop from my phone. My phone does not appear in Explorer/Network regardless of which network connection I'm using G or N. If I connect it with a USB cable, yes it appears as a device in Windows 10. But that hardly seems relevant.
How would I test if Windows "sees" my phone??

Router settings:
N:
- Mixed mode is on
- channel and ch bandwidth are set to auto
- broadcast is on
- AP isolation is ON

G:
- set to G-only
- ch bandwidth is 20Mhz only
- ch is auto
- broadcast is on

I just turned off the AP isolation for N and CC still doesnt connect.
Everything else is either set to auto or N and G settings are the same.

No access restrictions or MAC filtering are in place.

My phone connects to the N network fine.
CC however, cannot connect to Calibre wirelessly using this network.

Want logs? No idea how to look at them on the phone.

[deraeler]

re: "SEE" the device....my Router shows my phone in the in the DHCP client list when I"m connected to either my G or N network.
Windows however does not "see" the phone at all. It does if I plug it in as disk device using a USB cable.
How would I get Windows to see the device over wireless?

[deraeler]

I see no disabled plugins, however I'm not sure which would be used by my Samsung S7.
Here's the Debug Device connection output:
calibre 3.4 embedded-python: True is64bit: False
Windows-10-10.0.15063-SP0 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '10', '10.0.15063')
Python 2.7.12+
Windows: ('10', '10.0.15063', 'SP0', u'Multiprocessor Free')
Interface language: None
USB devices on system:
(USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid8086&pid9d2f&rev0021 devinst=1),
USBDevice(vendor_id=0x8087 product_id=0xa2b bcd=0x10 devid=usb\vid_8087&pid_0a2b&rev_0010 devinst=2),
USBDevice(vendor_id=0x64e product_id=0x3401 bcd=0x11 devid=usb\vid_064e&pid_3401&rev_0011 devinst=3),
USBDevice(vendor_id=0x64e product_id=0x3401 bcd=0x11 devid=usb\vid_064e&pid_3401&rev_0011&mi_00 devinst=4))

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 {'{FCC10A27-C72B-47BE-8C52-4F00CC2324BF}': [{'addr': u'192.168.1.103', 'netmask': u'255.255.255.255', 'broadcast': u'192.168.1.103'}], '{87E8B76D-5237-11E7-BFE2-806E6F6E6963}': [{'addr': u'127.0.0.1', 'netmask': u'255.255.255.255', 'broadcast': u'127.0.0.1'}]}
No device is connected

Looking for devices...

Devices possibly connected: None

[theducks]

Turn OFF AP isolation if both are WiFi. That prevents WiFi connections between peers as a security measure. WiFi to Wired might work with that on, then again, it might protect you from all sniffing.
The router issues an IP since that is needed for an Outside connection.

[deraeler]

Windows 10 allows me to connect to my phone only uisng a "Direct Connection" , nad it does this over Bluetooth. I see the phone under Devices and PRinters when conected using this method. However it still doesnt show under "Network".
CC still does not connect.
I would expect this, as Bluetooth has nothing to do with whats going on here.
(or NOT going on here).

Lastly, file and print sharing are on, network discovery is on, Windows is allowed to manage homegroup settings, enabled file sharing for devices that use 40 or 56-bit encryption, anyone can read/write public folders.

So once again I fell like I'm making my computer vulnerable by opening up all these settings, but they still don't work! What on earth is going on?

This is undoubtedly a Windows 10 thing....Microsoft is the giant evil here, I'm certain of it. We just have to figure out what Bhudda's belly I need to rub here.

[DoctorOhh]

Originally Posted by deraeler

G works, N doesnt.
...~~~...

Router settings:
N:
- Mixed mode is on
- channel and ch bandwidth are set to auto
- broadcast is on
- AP isolation is ON

G:
- set to G-only
- ch bandwidth is 20Mhz only
- ch is auto
- broadcast is on

I just turned off the AP isolation for N and CC still doesn't connect.
Everything else is either set to auto or N and G settings are the same.

No access restrictions or MAC filtering are in place.

My phone connects to the N network fine.
CC however, cannot connect to Calibre wirelessly using this network.

The bottom line is the error is in your Router not with calibre / calibre companion. They don't care what WiFi protocol or band is being used. I have used a few routers over the last 5 years and CC has had no problems.

After you turned off the AP isolation did you reboot your router? This was most likely the source of your issue. If you did reboot then I would leave AP isolation off, power cycle the router and the phone and try again. Do you have a guest mode on your router? Often this feature also isolates wireless devices from the main network.

Logs wouldn't hurt, you can send them via cc by going to Settings - Other and scrolling to the bottom and selecting Email a debug log to Multipie. More info on submitting logs here.

[chaley]

There is too much here to use QUOTE.

• The two "bands" are really two SSIDs. It is the SSID that chooses the configuration, both in the router and in Windows. The band chosen is relevant only of the router is preventing cross-band or WiFi-to-cable communication.
• AP Isolation is probably the same thing as Wireless Isolation. If that is on then no device connected to that SSID will be able to talk with another device anywhere on the local network. You also might want to check if any other "isolation" is turned on.
• Because you are using two SSIDs then you are using two different Windows network configurations. The one you want CC to use (I think this is what you are calling the "N" network) must be set up in Windows as a "Private" network with "Discoverability" turned on.
• The fact that it works with one SSID (the one you are calling "G") means that probably the AV is not the culprit. However, because there are two SSIDs in use it is possible that the AV & Firewall are treating them differently.
• By "see each other" I meant that the device and the computer running calibre can exchange packets.
• Bluetooth and USB are not relevant. The device should not be visible in Windows Explorer under either Network or Device.
• I am almost certain that adding a WPA key to the "G" SSID won't break anything. That test will show that the problem isn't related to encryption.
• I am also almost certain that if you allow the "G" SSID to use the "N" bands then things will continue to work. If you try this experiment, don't try the WPA key experiment at the same time. The rule: change only one thing at a time.
• I understand that your computer is connected to the router by cable. That opens the door for yet another kind of "isolation": preventing wireless-to-cable communication.

Given that you turned AP Isolation off, the first place I would check would be the Windows Networking setup for the "N" SSID. I would also do what DoctorOhh suggested: reboot the router after changing the configuration.

[deraeler]

I"m sick of losing my posts, this forum/board has issues.

[chaley]

Originally Posted by deraeler

I"m sick of losing my posts, this forum/board has issues.

My apologies for your difficulties.

FWIW: I have never lost a post on mobileread.

[deraeler]

unsecuring my G network proves nothing, we know this works over an unsecured (my N) network

yes I rebooted my router

network is discoverable

of course everything is private, its behind my router and my firewall.
no cabled connection, all wireless, no idea where that came from.

I dont need to hear stories about others' routers, sorry but I just dont care. As usual the solution is to throw more money at it, go buy a Mac and a new router.

I have shown you all of my settings. I"m running on an unsecured network because of your app...which is unacceptable.

I'm sure microsoft is to blame, nothing works as its supposed to and they wont support it, again.

you cant fix what they intentionally and repeatedly break.

[deraeler]

sorry I got em backwards n is secured g is not, I'm no network expert.

No problem sending logs, tell me what and how.

I can't stress enough how simple this network setup is, I mean it couldnt be more basic.
This really shouldnt be this complicated.