Enabled echo/ping requests as advised by @DNSB, following both these tutorials:
https://kb.iu.edu/d/aopy and
https://www.howtogeek.com/howto/wind...ista-firewall/. For some reason this didn't allow pinging immediately, even after a restart. But it did work later magically, somehow! (Two things I did during this time: Changed WiFi security from WPA/WPA2 to WPA2 and then router got restarted.)
Also, during the time the above wasn't working, I looked into other suggestions.
Quote:
Originally Posted by theducks
additionally: Some (most) WiFi routers block connections on the same LAN by default.
Also, both must use the same band. 2.4 or 5.0
Having the host on a wired network is a Plus
|
Checked router settings. Didn't find any isolation or LAN blocking settings.
Confirmed both computers are on same band (2.4 GHz).
Quote:
Originally Posted by chaley
Assuming wifi, in addition: - Both machines must be on the same SSID.
- The SSID must not be a "guest network".
- To add to @theducks first line, the router must not have "Wireless Isolation" (or something similarly named) turned on.
|
Both machines are on the same SSID i.e. showing same router name. I don't how it could be done any other way.
Nope, not signed into guest network.
No Wireless isolation or related settings found.
Anyway, the issue has been resolved by enabling pinging on the Windows 10 device hosting Calibre Content Server.
Thank you so very much!
