I have added printers in the past using system-config-printer, but something has changed on our network, I can no long use the tool on remote hosts, at least not on RHEL 5 hosts. So I brought up a Firefox browser on the remote host. Using http://127.0.0.1:631 I was able to add a network printer. I can print a test page to it from CUPS, but can't print to it from the command line. When I try it using the name I gave it during the CUPS setup, I get:

Try restart cups first using the cups script at /etc/init.

OK, I restarted cups. The printer is way over in another building, so I will need to walk back over to check it.

My /etc/printcap looks like this:

Full Qualified Domain Name:HP Laserjet 4000:rm=hostname of machine I am trying to print from: rp= FQDM

If I lp -d FQDM /etc/hosts

I get the error still, even after restarting CUPS.

OK, there were a number of problems, but the biggest was a file under /etc/cups called client.conf. It was pointing to some nonexistant server. I just removed the entry for the clients and now I can administer the clients remotely. I removed the printer I had added, added it back using system-config-printer and restarted cups. Works now.

If you use an HP Printer, try using the hplip package and driver for CUPS.

I have two HP, All-in-One printers that are "network" connected using wire. I'm having trouble getting
them added to my various workstations. I'm using HPLIP with CUPS for printer administration.

On my server/workstation (linux mint 16 KDE), both devices appear and seem to operate normally.

On my laptop/workstation (linux mint 15 Cinnamon), I can only see one device and half the other.

Since both printers are All-in-One, the print, scan, fax, and copy. HPLIP creates two devices: xxx_prt and xxx_fax.
When I say that I see a device, that means I see the _prt and _fax variants. In the case of "half"
that means I only see the _fax variant of the device in question.

Both Apple(R) Mac(tm) and Micro-$oft(R) Windows-7(tm) see and operate both devices without trouble.

QUESTION PART-II
What are the benefits and liabilities of using the SHARE option on network attached, CUPS printers?
Here is my thinking:

When a workstation requests something printed, the applications send the data to the queue on the local workstation. That queue then connects to the device and manages sending the data. When the data sending is complete,
the queue disconnects from the device -- after a configured delay -- so that some other queue can use the printer.

If the printer is "shared", things work the same way but with an extra step. The local workstation queue forwards
the data to the appropriate queue on some other workstation. That workstation connects to the device and manages the
output.

Given a laptop workstation that goes walk-about, shared printers at the server workstation seem to make sense.
I could queue output directly if I'm going to be in the office. If I'm leaving, I could queue it to the server,
shutdown and walk-about letting the server finish the output.

Thanks in advance,
~~~ 0;-Dan