On Wednesday 24 December 2008 00:03:46 Mick wrote: > If you are using SSL certificates you must set up the correct domain > name, with regards to what the client machines see on the intranet/LAN. > Clearly the IP address is not a FQDN and the certificate check fails. > So, you want your common name (CN = serv.ethnet or whatever) to be the > same with the name that your server is seen by the client in the LAN and > this may involve setting up your router to resolve serv.ethnet to > 192.168.2.2, or adding an entry in your client's /etc/hosts file to this > effect.
I'm not using SSL certificates, or not as far as I know. Every host on the LAN has serv.ethnet in its hosts file, and dnsmasq on the gateway also knows about it - of course. The problem is not in name resolving. Both the cups server and the box running the Web browser are on the same LAN segment. I've just checked all the boxes' hosts files and they're all correct. > To see what's failing (which could well be related to the http:// ir > ipp:// path to the printer being incorrect) you need to increase the > verbosity of CUPS in its configuration file and then have a close look > at: > > /var/log/cups/access_log > /var/log/cups/error_log Good idea. I'll do that. Thanks. -- Rgds Peter
