print server

DJOtaku · 10-04-2005, 07:56 PM

I set up a printer on a debian sarge machine using foomatic/cups/hpijs. The printer works as I can send stuff to the printer using the debian machine.

So on the client machine I went to the cups web page. And for URI connection I have
http://192.168.0.102:631/ipp

When I try to print I get the error:
"Unable to get printer status (client-error-forbidden)!"

and on the print server, the printer is idle. I think it has something to do with permissions, but I'm not 100% sure.

Any help would be fantastic!

Thanks,

Tinkster · 10-05-2005, 02:55 AM

Just enable browsing on both and don't worry about that stuff.
CUPS will then automatically pick the printer up.

And to be able to assess whether that entry is correct or not
we'd need to know how the printer is attached to the server.

Chances are that it REALLY should look like this:
ipp://server:631/printers/queuename

Cheers,
Tink

DJOtaku · 10-06-2005, 09:45 PM

how do I enable browsing? (please remember I'm limited to text on my print server)

Thanks,

Tinkster · 10-06-2005, 09:52 PM

vim cupsd.conf
/Browsing Options

... and then start reading ;} The file is very well documented
(at least in Slackware it is) and quite self-explanatory.

Cheers,
Tink

DJOtaku · 10-07-2005, 05:05 PM

did as you said and now I can see the printer.

To be more specific, I set Browsing On
and BrowsingAddress @LOCAL

However, whenever I try to do anything (such as print a test page), it gives me a page that says:

Forbidden
You don't have permission to access that on this server.

DJOtaku · 10-07-2005, 05:21 PM

I also still have this error

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

Tinkster · 10-07-2005, 05:39 PM

Fire vim back up, and look for

Code:

<Location />
Order Deny,Allow
Deny From All
Allow From 127.0.0.1
</Location>

and other similar entries underneath it. A good tip for
further assessment of cups-problems.
Stop CUPS.
Set the "Log level" from info to debug2
Delete the old log
start CUPS
attempt to print
stop CUPS
copy the newly created error_log away
Change the Log Level back to info
restart CUPS

In the saved copy of the big log look for lines that begin with
and e, and closely examine those and their surroundings.

Cheers,
Tink

DJOtaku · 10-07-2005, 05:48 PM

Thanks a lot! Somehow I missed those entries - now its working! You're so awesome!

Tinkster · 10-07-2005, 05:59 PM

Most welcome :}

If you have a few seconds to spare you can click that
affero-button, too ;)

Cheers,
Tink