Re: CUPS Nightmare

[Bill Johnson]

Thanks, Erwin, for the reply.

I have tried a couple of things based on the good responses from this 
list.

I now have 2 queues defined on the server.  One is called HP841C and it is 
intended to be used for printing from the server.  It is defined with the 
correct driver for the HP841C printer.  The other queue on the server is 
called HP841C_SHARED and it is set up as a raw queue.  I used the Redhat 
printer config tool to set this latter queue as shared.  The first queue 
is not shared.

On the laptop, when I look in CUPS (http://localhost:631), I can see both 
printers, but I cannot print to either.  If I try to print a test page to 
the HP841C_SHARED queue it prints many pages of junk, like what you would 
expect when the driver is wrong.  

If I try to create a queue on the laptop (via CUPS) and point it at the 
HP841C_SHARED queue on the server, using any of the protocols that are 
listed (ipp, lpr, etc., - I've tried every one), I cannot print a test 
page at all.  When I try, I get various messages listed on the CUPS 
printer page, such as "Remote host did not accept control file (112)".

I am very confused by the fact that I need to use the Redhat printer 
config tool for some portion of this process, and the CUPS web interface 
for others.  I don't understand how these two tools play together.

And, the main problem remains. I cannot yet print from my laptop.  I can 
print from the server, but nothing I do lets me print from the laptop.

If there is any additional information I can provide to this list that 
will help get this resolved, please let me know what I need to share.  I 
would really like to get this working without having to go back to Redhat 
8 or something I know works.

Thanks again for all the help!
Bill Johnson


On Sat, 25 Oct 2003, Erwin J. Prinz wrote:

>  Bill:
>  
>  I am using CUPS on a server with samba to print from Windows computers. 
>  When switching from "lpd" to "CUPS", I had to make a fundamental
> change 
>  to the configuration on the server running CUPS. I had to install TWO 
>  print queues, one for local printing from the server, and another one 
>  from printing from a different computer via the server. The difference 
>  between the queues is that the "local" one has a driver defined (e.g. 
>  Optra E310), and the "server" one has "raw print queue" set in the 
>  "printer driver" tab. I believe that the client computer has a driver, 
>  sends "raw" print commands to the server, and the server just passes the 
>  commands to the printer. You may want to try a "raw" print queue on the 
>  server.
>  
>  Hope this helps.
>  
>  Best regards, Erwin
>   
-- 
Bill Johnson

"Call unto me, and I will answer thee, and shew thee great and 
mighty things that thou knowest not."  Jeremiah 33:3

CUPS Nightmare

[Tim Waugh]

On Mon, Oct 27, 2003 at 09:16:21PM -0500, Bill Johnson wrote:

>  Thanks, Erwin, for the reply.
>  
>  I have tried a couple of things based on the good responses from this 
>  list.
>  
>  I now have 2 queues defined on the server.  One is called HP841C and it is 
>  intended to be used for printing from the server.  It is defined with the 
>  correct driver for the HP841C printer.  The other queue on the server is 
>  called HP841C_SHARED and it is set up as a raw queue. 
Why a raw queue?  I think you just need the one queue, and set it shared.

On the laptop, or any client, there is no need to set a queue up.
Just enable remote queue browsing ("Automatically find remote shared
queues") with the Printing tool from the menu, and print directly to
those queues by name.

For simple situations like this there is no need to use the web GUI.
The graphical tool is meant to be a simple replacement, covering the
most often-used functionality. (I'm aware there are large gaps for
more sophisticated needs.)

Tim.
*/

CUPS Nightmare

On Tue, Oct 28, 2003 at 09:49:15AM +0000, Tim Waugh wrote:
>  On Mon, Oct 27, 2003 at 09:16:21PM -0500, Bill Johnson wrote:
>  
>  > Thanks, Erwin, for the reply.
>  > 
>  > I have tried a couple of things based on the good responses from this 
>  > list.
>  > 
>  > I now have 2 queues defined on the server.  One is called HP841C and it is 
>  > intended to be used for printing from the server.  It is defined with the 
>  > correct driver for the HP841C printer.  The other queue on the server is 
>  > called HP841C_SHARED and it is set up as a raw queue.
>  
>  Why a raw queue?  I think you just need the one queue, and set it shared.
>  
>  On the laptop, or any client, there is no need to set a queue up.
>  Just enable remote queue browsing ("Automatically find remote shared
>  queues") with the Printing tool from the menu, and print directly to
>  those queues by name.
>  
>  For simple situations like this there is no need to use the web GUI.
>  The graphical tool is meant to be a simple replacement, covering the
>  most often-used functionality. (I'm aware there are large gaps for
>  more sophisticated needs.)
>  
>  Tim.
>  */ 
Because HP printers have a built in JetDirect interface and its queue
name is supposed to be raw. This works if the interface is external but
if it is internal I get similar errors unless I name the queue
something other than raw.


-- 
-------------------------------------------
Aaron Konstam
Computer Science
Trinity University
715 Stadium Dr.
San Antonio, TX 78212-7200

telephone: [phone]
email:[e-mail]

CUPS Nightmare

[Bill Johnson]

On Tue, 28 Oct 2003, Tim Waugh wrote:

>  On Mon, Oct 27, 2003 at 09:16:21PM -0500, Bill Johnson wrote:
>  
>  > Thanks, Erwin, for the reply.
>  > 
>  > I have tried a couple of things based on the good responses from this 
>  > list.
>  > 
>  > I now have 2 queues defined on the server.  One is called HP841C and it is 
>  > intended to be used for printing from the server.  It is defined with the 
>  > correct driver for the HP841C printer.  The other queue on the server is 
>  > called HP841C_SHARED and it is set up as a raw queue.
>  
>  Why a raw queue?  I think you just need the one queue, and set it shared.
>  
>  On the laptop, or any client, there is no need to set a queue up.
>  Just enable remote queue browsing ("Automatically find remote shared
>  queues") with the Printing tool from the menu, and print directly to
>  those queues by name.
>  
>  For simple situations like this there is no need to use the web GUI.
>  The graphical tool is meant to be a simple replacement, covering the
>  most often-used functionality. (I'm aware there are large gaps for
>  more sophisticated needs.)
>  
>  Tim.
>  */
>   
This makes perfect sense to me, and is what I would like to set up.  I'm 
running KDE, and the printing tool from the system settings menu does not 
include any such option (Automatically find remote shared queues) that I 
can see.  I looked at the print config in the KDE control panel, and don't 
see any such option there, either.  Where is this option that you 
describe.  I'd like to try it.


 -- Bill Johnson

"Call unto me, and I will answer thee, and shew thee great and 
mighty things that thou knowest not."  Jeremiah 33:3

CUPS Nightmare

[Tim Waugh]

On Tue, Oct 28, 2003 at 06:19:58PM -0500, Bill Johnson wrote:

>  This makes perfect sense to me, and is what I would like to set up. 
> I'm 
>  running KDE, and the printing tool from the system settings menu does not 
>  include any such option (Automatically find remote shared queues) that I 
>  can see.  I looked at the print config in the KDE control panel, and don't 
>  see any such option there, either.  Where is this option that you 
>  describe.  I'd like to try it. 
Actions->Sharing (General tab, if there are tabs)

Tim.
*/