[TriLUG] cups and IPP: yet another question

Greg Brown gregbrown at mindspring.com
Tue Sep 14 13:06:06 EDT 2004


I've read.. I've googled, etc, etc.

I want to be able to print to my server, which is running cups, from 
other cups clients.  I have a LaserJet 1200 attached to the server 
(running RH 9 now, soon to be CentOS) via a USB cable.  I can print to 
the printer from the CUPS admin page (http://127.0.0.1:631) using 
"print test page".

Before I did anything I changed my IP Tables to allow incoming requests 
over 631.

My CUPS print queue name is "LinuxJet".  I have made the following 
changes to /etc/cups/cupsd.conf:

(per a page I found google-ing):
#Port 80
#Port 443
#Port 631
Listen 127.0.0.1:631
Listen 192.168.15.50:631
# Listen 127.0.0.1:80
# Listen 192.168.15.50:80

BrowseAllow 192.168.15.0/24

<Location /printers/LinuxJet>
AuthType None
Order Deny,Allow
Deny From All
Allow From 127.0.0.1, 192.168.15.0/24
</Location>


Still, when I try to print from a remote CUPS system I get the 
following errors:

(on the client side):
(url: http://192.168.15.50:631/printers/LinuxJet?op=print-test-page)
Forbidden
You don't have permission to access the resource on this server.

(on the server side - after kicking up the log level to debug)
  D [14/Sep/2004:12:55:53 -0400] AcceptClient() 4 from 
192.168.15.199:631.
D [14/Sep/2004:12:55:54 -0400] ReadClient() 4 GET 
/printers/LinuxJet?op=print-test-page HTTP/1.1
D [14/Sep/2004:12:55:54 -0400] SendError() 4 code=403
D [14/Sep/2004:12:56:25 -0400] CloseClient() 4


Based on this I can see that the two systems are communicating - if the 
two were not communicating in some way then I would have no debug 
information on the server.  So, where am I going wrong?  The client 
side is a Mac OS 10.2.x machine and I have the remote printer set up as 
ipp://192.168.15.50/printers/LinuxJet.  The queue type is "RAW" (per 
another google page).

Does anyone have a working cupsd.conf file that accepts IPP requests 
from the network that I can diff against mine?

Greg




More information about the TriLUG mailing list