I'm trying to get remote printing to work, and there's clearly some very basic problem or misconfiguration I'm encountering. My hostname is SUILLUS and the printer on it, configured with CUPS, is "lp". I can print to lp perfectly well if I refer to it directly. However, if I try to view lp as a remote printer, I get "client-error-not-found". The following output shows the problem: pwa@suillus:~> lpstat -h suillus -p printer lp is idle. enabled since Jan 01 00:00 printer lpraw is idle. enabled since Jan 01 00:00 pwa@suillus:~> echo hello | lpr -P lp@suillus lpr: unable to print file: client-error-not-found I try to access lp from a different machine using the same command, I get the same error. I'm treating the local host as a remote host because that simplifies testing; I can do everything on one machine. I also note that I can access filesystems on suillus via nfs. Moreover, echo hello | lpr -P lp prints a page with "hello", as it should. Paul Abrahams
On Fri, 16 Jan 2004 14:47, Paul W. Abrahams wrote:
I'm trying to get remote printing to work, and there's clearly some very basic problem or misconfiguration I'm encountering. My hostname is SUILLUS and the printer on it, configured with CUPS, is "lp". I can print to lp perfectly well if I refer to it directly. However, if I try to view lp as a remote printer, I get "client-error-not-found".
I suggest you look at the config settings in /etc/cups/cupsd.conf especially the security settings. Also /etc/cups/client.conf should have the name of the printer server in it. Also have a look at http://susefaq.sourceforge.net/cups.html although it is a bit out of date it covers some of the problems configuring cups. -- Regards, Graham Smith ---------------------------------------------------------
I'm wondering if the "lp@suillus" notation is really valid, even though the CUPS user documentation says it's the way to refer to a remote printer. I discovered that the command: echo hello | lp -h suillus -d lp works correctly and prints "hello" on suillus's printer even though the apparently equivalent command echo hello | lpr -P lp@suillus gives the client-error-not-found error. Paul Abrahams
Hello, On Jan 15 23:42 Paul W. Abrahams wrote (shortened):
echo hello | lp -h suillus -d lp works correctly and prints "hello" on suillus's printer even though the apparently equivalent command echo hello | lpr -P lp@suillus gives the client-error-not-found error.
Yes. It works at least with CUPS 1.1.15 (SuSE Linux 8.1 and SLES8) but is doesn't work at least with CUPS 1.1.19 (SUSE LINUX 9.0). I posted a Software Trouble Report: http://www.cups.org/str.php?L522 By the way: If you use CUPS Browsing then you don't need "@server" or "-h server". The "name@server" stuff had never worked well for the BSD-like commands. For example "lpq -P name@server" had never worked. Therefore I never mentioned "name@server" for the BSD-like commands in the manuals and described only the System V style commands (which work well) in case of remote queues - see the Administration Guide - "Command-Line Tools for the CUPS Printing System" - "Managing Remote Queues" Additionally please note that the ordering of the options is of importance - see the Administration Guide. Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Fri, 16 Jan 2004 14:47, Paul W. Abrahams wrote:
I'm trying to get remote printing to work, and there's clearly some very basic problem or misconfiguration I'm encountering. My hostname is SUILLUS and the printer on it, configured with CUPS, is "lp". I can print to lp perfectly well if I refer to it directly. However, if I try to view lp as a remote printer, I get "client-error-not-found".
I suggest you look at the config settings in /etc/cups/cupsd.conf especially the security settings. Also /etc/cups/client.conf should have the name of
On Thursday 15 January 2004 11:30 pm, Graham Smith wrote: the
printer server in it.
Is the client.conf file supposed to be manipulated directly rather than by, say, some Yast2-like program or the CUPS administrative facilities? As I noted in another message, the fact that the command echo hello | lp -h suillus -d lp works correctly suggests that security settings aren't the problem. Paul Abrahams
On Fri, 16 Jan 2004 15:46, Paul W. Abrahams wrote:
On Thursday 15 January 2004 11:30 pm, Graham Smith wrote:
I suggest you look at the config settings in /etc/cups/cupsd.conf especially the security settings. Also /etc/cups/client.conf should have the name of the printer server in it.
Is the client.conf file supposed to be manipulated directly rather than by, say, some Yast2-like program or the CUPS administrative facilities?
What I have found is that it is easier to add the cups server name directly to /etc/cups/client.conf It does not interfer with the operation of Yast or Cups admin.
As I noted in another message, the fact that the command
echo hello | lp -h suillus -d lp
works correctly suggests that security settings aren't the problem.
Paul Abrahams
Once you have setup client.conf all your printers on your server should appear on your remote clients. Then you should be able to use the following command to print a file to 'lp' on the server. lpr -P lp <filename> or lp -d lp <filename> As you note there is no need to specify a hostname unless you have multiple printers named the same on different servers. In that case it would be best to rename the printers to a more meaningful names. -- Regards, Graham Smith ---------------------------------------------------------
On Fri, 16 Jan 2004 14:47, Paul W. Abrahams wrote:
I'm trying to get remote printing to work, and there's clearly some very basic problem or misconfiguration I'm encountering. My hostname is SUILLUS and the printer on it, configured with CUPS, is "lp". I can print to lp perfectly well if I refer to it directly. However, if I try to view lp as a remote printer, I get "client-error-not-found".
I suggest you look at the config settings in /etc/cups/cupsd.conf especially the security settings. Also /etc/cups/client.conf should have the name of
On Thursday 15 January 2004 11:30 pm, Graham Smith wrote: the
printer server in it.
Also have a look at http://susefaq.sourceforge.net/cups.html although it is a bit out of date it covers some of the problems configuring cups.
That seems to have solved the problem. Now I just have to solve the same problem with respect to Samba -- Linux printers that Windows recognizes but can't print to because of some problem with the server name. Paul Abrahams
participants (3)
-
Graham Smith -
Johannes Meixner -
Paul W. Abrahams