On Tuesday 23 December 2008, Peter Humphrey wrote:
> On Monday 22 December 2008 18:00:52 BRM wrote:
[snip...]

> I let cups find the printer and I tell it to use the .ppd file I got from
> linuxprinting.org. It shows the printer configuration page, where I set A4
> paper, then I get a security error saying that I have attempted to
> establish a connection with 192.168.2.2 whereas the security certificate
> presented belongs to serv.ethnet. Guess what - serv.ethnet is the machine
> I'm working on and it has IP address 192.168.2.2. What is going on here? (I
> don't get this error when setting up my laser printer; only with this
> inkjet.)

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.

> On printing a test page I get "/usr/libexec/cups/filter/foomatic-rip
> failed" and job stopped.
>
> > On your client systems you add it as an IPP printer as the Network
> > Server's CUPS server is the IPP host.
>
> It would be nice to get that far. At present I can't get anything working
> at all without using hplip.

I am sorry but I have not followed all your previous threads on this subject - 
from my experience hplip should work straight out of the box.  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

HTH.
-- 
Regards,
Mick