CUPS problems

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Craig White
Date:  
Subject: CUPS problems
On Wed, 2004-01-28 at 07:56, Derek Neighbors wrote:
> der.hans said:
> > Am 27. Jan, 2004 schwätzte Deepak Saxena so:
> >
> >> I've got my server (Debian/stable) running cups connected to an HP1100
> >> over the parallel port and can print to it OK. My client machine
> >> (Debian/unstable) can see the printer on the network, but when I
> >> print, nothing happens. Looking at the error.log on the server, I
> >> see:
> >>
> >> D [27/Jan/2004:22:02:34 -0700] AcceptClient() 10 from 192.168.1.3:631.
> >> D [27/Jan/2004:22:02:34 -0700] ReadClient() 10 POST /printers/hp1100
> >> HTTP/1.1 D [27/Jan/2004:22:02:34 -0700] SendError() 10 code=403
> >> D [27/Jan/2004:22:02:35 -0700] CloseClient() 26
> >> D [27/Jan/2004:22:02:44 -0700] AcceptClient() 26 from 192.168.1.3:631.
> >> D [27/Jan/2004:22:02:44 -0700] ReadClient() 26 POST /printers/hp1100
> >> HTTP/1.1 D [27/Jan/2004:22:02:44 -0700] SendError() 26 code=403
> >> D [27/Jan/2004:22:02:45 -0700] CloseClient() 34
> >> ...
> >
> > Are you certain you've allowed the client access to print to the
> > printer?
> > I ran into something like this and was denied due to not having perms to
> > write to the queue.
>
>
>
> Definitely looks like a permissions problem. Look at cupsd.conf security
> section.
>
> Something like
>
> <Location />
> Order Deny,Allow
> Deny From All
> Allow From 127.0.0.1
> Allow From 192.168.1.0/24
> </Location>
>
> This should allow localhost plus, anything on 192.168.1.x, you might be
> able to use 192.168.1.* notation as well.
>
> A good trick would be
>
> <Location />
> Order Deny,Allow
> Deny From All
> Allow From 127.0.0.1
> @LOCAL
> </Location>
>
> Which should allow any local connections, but no remote connections. I
> have never tried it personally, but I hear good things. Make sure you
> restart cups after changing this file.

---
and if you access the printer as a windows printer via samba, you would
need to restart samba when you make changes and then restart cups, the
changes aren't reflected in samba unless you restart samba too.
Interestingly enough, cups printers shared via samba do not need sharing
to the @local/local_lan because cups gets the files from samba on the
localhost and samba handles the permissions from the various users.

Craig