View Single Post
Old 05-27-2015, 08:10 PM   #14
CRussel
(he/him/his)
CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.
 
CRussel's Avatar
 
Posts: 12,298
Karma: 80074820
Join Date: Jul 2010
Location: Sunshine Coast, BC
Device: Oasis (Gen3),Paperwhite (Gen10), Voyage, Paperwhite(orig), iPad Air M3
Quote:
Originally Posted by chaley View Post
Assuming that your server has two fixed IP addresses, doesn't entering one of them into each of the two sections of CC's Content server IP settings box solve the problem?

I can imagine why using automatic connection sometimes won't work. The server will broadcast one of its IP address using mDNS (bonjour) and CC will attempt to connect to that address. It is apparently broadcasting the one you normally don't use. You could fix this by telling the content server to use the NIC on the network you usually connect to by using the calibre tweak (What interfaces should the content server listen on (ID: server_listen_on)). Of course that will ensure that you can never connect on the other NIC.
I ended up forcing Calibre to only use the one NIC. It worked, but means I often have to switch wireless networks to connect. Annoying but not any worse than that.
CRussel is online now   Reply With Quote