Re: [tlug] cups and networking

[Scott Robbins <scottro@example.com>]

On Fri, May 18, 2007 at 01:54:40PM +0900, Darren Cook wrote:
> > 
> > <Location />
> > Order Deny,Allow
> > Deny From All
> > Allow From @LOCAL
> > </Location>
> 
> 
> I tried adding Allow From 172.16.1.* in various places, but no luck, so
> I added a whole new Location block:
> <Location /printers/HL2040>
> Order Deny,Allow
> Deny From All
> Allow From 127.0.0.1
> Allow From 172.16.1.*
> AuthType None
> Allow from All
> </Location>

First see if that one is the key.  Allow from all, put the allow line
before the deny line.  If that works, then you know it's something off
with the syntax you're using.  I believe it reads it in order, so it's
going to deny all and ignore the allow lines.  
> 
> 
> I tried Josh's suggestion of changing from that weird binary_p1 to the
> actual queue name of HL2040, but same thing.

That was my suggestion, but that's ok, as long as it's Josh, I don't
mind.  :)

> 
> I tried: ipp://172.16.0.2/ipp/port1
> and get "Unable to get printer status (client-error-forbidden)!"

k
> 
> 
> I'm confused. The CUPS docs says that ipp is the only supported
> protocol. 

CUPS docs are known for being horrible.  


Brother, and Josh, suggested using lpd. I wonder if I should
> bark up the ipp tree a bit more? Or maybe I should start barking up the
> smb tree as I will eventually need to get that working anyway.

The lpd line should work, I suspect it's the deny all and its location
in your conf file.  Did you see that link I posted?

As I said, I would change your location to order allow deny, allow all
and see if it prints.   (While doing that, comment out other allow
lines as well as deny lines, and deny from none.  The chances of someone
hacking in and printing from your printer are rather slim.)


If it does work, then you can play with the <Location>
section to figure out what's wrong.   If you have order allow deny, then
allow from local, you might wind up not allowing anything else.  (I
haven't done it that way, but it seems to me that various folks have run
into problems with that.)

> the server, plugging into my work machine, 30 seconds of configuration,
> and getting today's important documents printed. :-). If it wasn't for
> my wife's notebook I could just live without it networked...

If you don't do much printing, or if you two aren't frequently printing
at the same time, the easiest workaround is to get a $30-40 print server 
and just give the printer its own IP address.  Then, add it to the
various machines as a local printer with a TCP/IP port in Windows and in
cups use socket://xxx.xxx.xxx.xxx (where the xxx's are the IP address.)

It often saves a lot of aggravation. 


-- 

Scott Robbins

PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Oz: Sometimes when I'm sitting in class...you know, I'm not 
thinking about class 'cause that would never happen... I think 
about kissing you. And it's like everything stops, it's like, 
freeze frame: Willow kissage.