View Single Post
Old 11-21-2017, 12:40 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: 12,449
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by stumped View Post
But can you suggest why, with a new tablet install, the "find content server automatically" never works.
I have a simple lan.
The calibre content server is on a.static windows 10.pc, wired, no wifi, at internal ip 192.168.0.28 port 8080
.no.passwords.
the wifi tablets are.on the same.lan. but a manual entry of that ip is always needed at 1st setup. Afrer that, all is good
Something is preventing mDNS (bonjour) and UDP broadcasts getting exchanged between the tablets and calibre. In your case I suspect the culprit to be the home router, but it isn't a strong suspicion.

You should check that the devices are really on the same network. I assume that they all have IP addresses in the 192.168.0 range. It is possible that it is further subnetted, in which case you would need to use an IP address. On the calibre computer, us ipconfig to verify that the subnet mask is 255.255.255.0. If it is anything else then your network setup is probably the cause.

A calibre (not CC) debug log will tell you if calibre is receiving CC's "are you there" broadcasts. If it is not then the culprit is the firewall or AV on the calibre machine, or the home router. If it is but CC isn't hearing the reply then you can rule out the home router as the culprit.
chaley is offline   Reply With Quote