On 2010-04-04 04:02, Camaleón wrote:
On Sat, 03 Apr 2010 19:15:55 -0500, Ron Johnson wrote:
On 2010-04-03 18:50, Ron Johnson wrote: [snip]
(...)
Order allow,deny
Allow @LOCAL
So... did you finally try -reverse order- and it worked? Good to know :-)
I *did*, but there were other
On 2010-04-04 02:27, Liam O'Toole wrote:
On 2010-04-03, Ron Johnson wrote:
[snip]
Does "listen", in this case, also mean "listen for *requests* from
clients?"
Yes, it specifies the interface(s) the daemon will bind to in order to
receive requests from clients.
Should have realized tha
On Sat, 03 Apr 2010 19:15:55 -0500, Ron Johnson wrote:
> On 2010-04-03 18:50, Ron Johnson wrote: [snip]
(...)
>
>Order allow,deny
>Allow @LOCAL
>
So... did you finally try -reverse order- and it worked? Good to know :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-u
On 2010-04-03, Ron Johnson wrote:
> On 2010-04-03 15:12, Liam O'Toole wrote:
>> On 2010-04-03, Ron Johnson wrote:
>>> On 2010-04-03 14:31, Liam O'Toole wrote:
On 2010-04-03, Ron Johnson wrote:
---SNIP---
> r...@diningroom:~# lpstat -v -h haggis
> lpstat: Connection refused
On 2010-04-03 18:50, Ron Johnson wrote:
[snip]
(server)# cupsctl --share-printers
That rewrote a big chunk of /etc/cups/cupsd.conf. Now it looks like:
LogLevel warn
MaxLogSize 0
SystemGroup lpadmin
Port 631
Listen /var/run/cups/cups.sock
Browsing On
BrowseOrder allow,deny
BrowseAllow all
Browse
On 2010-04-03 18:39, Andrei Popescu wrote:
On Fri,02.Apr.10, 21:10:27, Ron Johnson wrote:
Hi,
I did this once a *long* time ago, but don't remember how. Also,
I've read the (seemingly relevant sections of the sorely lacking)
CUPS SAM, and Googled around to no avail.
Yeah, same here a month o
On 2010-04-03 15:12, Liam O'Toole wrote:
On 2010-04-03, Ron Johnson wrote:
On 2010-04-03 14:31, Liam O'Toole wrote:
On 2010-04-03, Ron Johnson wrote:
---SNIP---
r...@diningroom:~# lpstat -v -h haggis
lpstat: Connection refused
Are you sure the cups daemon is listening on haggis' external in
On Fri,02.Apr.10, 21:10:27, Ron Johnson wrote:
> Hi,
>
> I did this once a *long* time ago, but don't remember how. Also,
> I've read the (seemingly relevant sections of the sorely lacking)
> CUPS SAM, and Googled around to no avail.
Yeah, same here a month or so ago...
> My server has a print
On 2010-04-03, Ron Johnson wrote:
> On 2010-04-03 14:31, Liam O'Toole wrote:
>> On 2010-04-03, Ron Johnson wrote:
>> ---SNIP---
>>> r...@diningroom:~# lpstat -v -h haggis
>>> lpstat: Connection refused
>>
>> Are you sure the cups daemon is listening on haggis' external interface?
>> From the cli
On 2010-04-03 14:31, Liam O'Toole wrote:
On 2010-04-03, Ron Johnson wrote:
---SNIP---
r...@diningroom:~# lpstat -v -h haggis
lpstat: Connection refused
Are you sure the cups daemon is listening on haggis' external interface?
From the client, try 'telnet haggis 631' or 'nmap -p 631 haggis', a
On 2010-04-03 13:45, Axel Freyn wrote:
[snip]
I think, you should rename this file to "/etc/cups/client.conf" - that's
what it is called on my machines;-)
Fixed that.
[snip]
Well, there are 3 possibilites:
[snip]
3) you install on the client only the cups-client, and add in the file
/
On 2010-04-03, Ron Johnson wrote:
---SNIP---
> r...@diningroom:~# lpstat -v -h haggis
> lpstat: Connection refused
Are you sure the cups daemon is listening on haggis' external interface?
>From the client, try 'telnet haggis 631' or 'nmap -p 631 haggis', after
installing the corresponding package
On 2010-04-03 13:42, Liam O'Toole wrote:
On 2010-04-03, Ron Johnson wrote:
[snip]
You seem to be using /etc/cups/cups.conf on the client. What you need is
/etc/cups/client.conf.
Thanks for catching that.
$ cat /etc/cups/client.conf
ServerName haggis
Hi Ron,
>
> My server has a print queue that looks like this:
> $ lpstat -v
> device for Dell_3100cn: socket://192.168.1.11
> device for dell_310...@haggis: socket://192.168.1.11
> device for PDF: cups-pdf:/
>
> The server's /etc/cups/cupsd.conf looks like:
> Browsing On
> BrowseOrder allow,deny
>
On 2010-04-03, Ron Johnson wrote:
> On 2010-04-03 04:15, Liam O'Toole wrote:
---SNIP---
>>
>> I got broadcasting to work by setting BrowseAddress to the IP address of
>> the interface to broadcast on.
>
> Do you mean haggis' IP address???
>
Yes.
>>Alternatively y
On 2010-04-03 04:17, Nigel Henry wrote:
[snip]
Now my /etc/cups/cupsd.conf looks like:
Browsing On
BrowseOrder allow,deny
BrowseAllow 192.168.1.0/24
BrowseAddress @IF(eth0)
BrowseLocalProtocols CUPS dnssd
DefaultAuthType Basic
Order allow,deny
Allow from 192.168.1.*
Yes. On the client OS
On Sat, 03 Apr 2010 12:21:33 -0500, Ron Johnson wrote:
> On 2010-04-03 04:42, Camaleón wrote:
(...)
>> allow,deny - Deny requests by default, then check the Allow lines
>> followed by the Deny lines
>> ***
>>
>>
> So you think I should reverse the order of the lines in the Location
> tag?
Yes
On 2010-04-03 04:15, Liam O'Toole wrote:
On 2010-04-03, Ron Johnson wrote:
Hi,
I did this once a *long* time ago, but don't remember how. Also,
I've read the (seemingly relevant sections of the sorely lacking)
CUPS SAM, and Googled around to no avail.
My server has a print queue that look
On 2010-04-03 04:17, Nigel Henry wrote:
[snip]
Your printers.conf on the server machine should have a line "Shared Yes".
[snip]
Accepting Yes
Shared No
Got that:
Accepting Yes
Shared Yes
If you have active firewalls on your machines, make sure that IPP is allowed
in both directions.
On 2010-04-03 07:51, Rob Owens wrote:
[snip]
On my lenny system, I find options for this on the "administration" tab
of the cups web interface. http://localhost:631
There's a "show printers..." and a "share printers..." checkbox.
Is that a vote for the cups server package also being on the c
On 2010-04-03 04:42, Camaleón wrote:
On Fri, 02 Apr 2010 21:10:27 -0500, Ron Johnson wrote:
(...)
Allow from 192.168.1.*
Order allow,deny
I would make a little test:
Order allow,deny
Allow from 192.168.1.*
As per CUPS manual:
***
The Order directive defines the default acc
On Fri, Apr 02, 2010 at 09:10:27PM -0500, Ron Johnson wrote:
> Hi,
>
> I did this once a *long* time ago, but don't remember how. Also, I've
> read the (seemingly relevant sections of the sorely lacking) CUPS SAM,
> and Googled around to no avail.
>
> My server has a print queue that looks like
On Fri, 02 Apr 2010 21:10:27 -0500, Ron Johnson wrote:
(...)
>
>Allow from 192.168.1.*
>Order allow,deny
>
I would make a little test:
Order allow,deny
Allow from 192.168.1.*
As per CUPS manual:
***
The Order directive defines the default access control. The following
value
On Saturday 03 April 2010 04:10, Ron Johnson wrote:
> Hi,
>
> I did this once a *long* time ago, but don't remember how. Also,
> I've read the (seemingly relevant sections of the sorely lacking)
> CUPS SAM, and Googled around to no avail.
Hi Ron.
Can't help much on configuring the machine with t
On 2010-04-03, Ron Johnson wrote:
> Hi,
>
> I did this once a *long* time ago, but don't remember how. Also,
> I've read the (seemingly relevant sections of the sorely lacking)
> CUPS SAM, and Googled around to no avail.
>
> My server has a print queue that looks like this:
> $ lpstat -v
> devi
Hi,
I did this once a *long* time ago, but don't remember how. Also,
I've read the (seemingly relevant sections of the sorely lacking)
CUPS SAM, and Googled around to no avail.
My server has a print queue that looks like this:
$ lpstat -v
device for Dell_3100cn: socket://192.168.1.11
device
26 matches
Mail list logo
