MobileRead Forums - View Single Post

chaley · 07-21-2017, 02:43 AM

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.

07-21-2017, 02:43 AM	#11
chaley Grand Sorcerer Posts: 12,476 Karma: 8025702 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	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.