Configuring CUPS clients

From Admin-SIG

Information is sparse on getting CUPS to talk to CUPS. It seems that most published information is getting CUPS to run locally, and to send and receive print jobs to other operating systems.

CUPS client to CUPS server

In order to get a CUPS client to recognize a remote CUPS server, make sure a line like:

    ServerName MyCUPSserverMachine

appears in your /etc/cups/client.conf.

Similarly, make sure that your CUPS server is configured to accept connections from your LAN, with a section like:

    <Location />
        Order Deny,Allow
        Deny From All
        Allow From 127.0.0.1
        Allow From 192.168.1.7/24
        Allow From @LOCAL
    </Location>

Also, be sure it allows local browsing with a line like:

    BrowseAllow @LOCAL

In /etc/cups/cupsd.conf on MyCUPSserverMachine.

Otherwise you may get errors when trying to print from 192.168.1.7/24 machines (i did). I have not tried the @LOCAL setting, but it may work. It was suggested by others after I found that the 192.168.1.7/24 line worked for me.

It is possible that this is configurable form the CUPS WWW interface (http://localhost:631) or perhaps with foomatic-gui (which is package foomatic-gui in Debian), but the method to change these settings is not obdvious, at least not to this author.


From Windows XP and 2000

Modern versions of Windows XP (and perhaps some 2000) will speak directly to a CUPS server. Add a network printer, pointing to a URL like:

     http://192.168.1.1:631/printers/hp1100

where hp1100 is a printer name on the CUPS server on the machine at IP 192.168.1.1.

You can install the print driver to the RAW mode in CUPS as usual for windows, or install a generic PS or PDF driver and let the CUPS server convert to the local printer language.