Unix Technical Forum

Unable to get printer status (client-error-forbidden)!

This is a discussion on Unable to get printer status (client-error-forbidden)! within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> If you have tried to set up a shared printer using cups via the web setup(localhost:631), you have probably ...


Go Back   Unix Technical Forum > Unix Operating Systems > Slackware Linux Support

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-20-2008, 07:30 AM
4partee
 
Posts: n/a
Default Unable to get printer status (client-error-forbidden)!

If you have tried to set up a shared printer using cups via the web
setup(localhost:631), you have probably had this error message.

Viewing the documentation under Help, one is informed that the printers
are set up to share by default. This is a misstatement.

Given the above, you will have likely futzed around trying to figure out
what is wrong with:

file:/path/to/filename.prn
http://hostname:631/ipp/
http://hostname:631/ipp/port1
ipp://hostname/ipp/
ipp://hostname/ipp/port1
lpd://hostname/queue
socket://hostname
socket://hostname:9100

during printer setup from the client. Here is an example that worked for
me:

Description:
Location:
Printer State: idle, accepting jobs.
": Print file accepted - job ID 21."
Device URI: http://enterprise:631/printers/hp656

Now, the problem is with permissions; and it is caused by a restriction
in /etc/cups/cupsd.conf, a file that is not configurable by the web setup.

Look in the file for:
<Location />
Order Deny,Allow
Deny From All
Allow From 127.0.0.1
</Location>

As you see, access to anything cups is restricted, so comment out
the three commands. You could instead, add an Allow From 192.168.0.0/16.
Like the surgeon said, suture self.

--
John & Sue
'04 GMC Safari
'99 Starcraft Starflyer (Shuttlecraft)

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-20-2008, 07:30 AM
Mr. Boy
 
Posts: n/a
Default Re: Unable to get printer status (client-error-forbidden)!

4partee,

The web interface for CUPS is only a tool to setup printers, but is not
intended to do administration beyond creating printer devices, classes
or printing task monitoring and management. This is not to setup or
configure the service itself.

as everything in slackware (thank god & Patrick for this) you must set
it up in a nice powerful cli ... (command-line-interface) the plain-old
prompt.

there are some GUI tools to do it, like KDE's Printer Manager...

But to keep it safe, cupsd.conf must be edited by root using your
favorite editor... like vi or joe...

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-20-2008, 07:30 AM
4partee
 
Posts: n/a
Default Re: Unable to get printer status (client-error-forbidden)!

On Thu, 07 Apr 2005 09:12:53 -0700, Mr. Boy wrote:

> 4partee,
>
> The web interface for CUPS is only a tool to setup printers, but is not
> intended to do administration beyond creating printer devices, classes
> or printing task monitoring and management. This is not to setup or
> configure the service itself.


You missed my idea completely. *-)

The problem was that the documentation stated that the default was to
share the printer, and the config file denied sharing. The default config
was more suited to a workstation setup. I was not so concerned with 'how'
to edit the config file.

I was just showing how to get cups to share a printer as I'm sure many
would expect to be the default behavior.

Thank goodness I use Slackware and therefor am not afraid of CLI.



--
John & Sue
'04 GMC Safari
'99 Starcraft Starflyer (Shuttlecraft)

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-20-2008, 07:31 AM
Mr. Boy
 
Posts: n/a
Default Re: Unable to get printer status (client-error-forbidden)!

Oh... sorry about that.... i thought your were saying something else...

But you are completely right.... the default conf, is not shared at
all...

and yes, slackware is the best.. there is nothing like slackware's CLI

Cheers!

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 06:38 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
www.UnixAdminTalk.com