Re: CUPS broadcasting print queue availability
On 2010-04-03, Ron Johnson <firstname.lastname@example.org> wrote:
> On 2010-04-03 15:12, Liam O'Toole wrote:
>> On 2010-04-03, Ron Johnson <email@example.com> wrote:
>>> On 2010-04-03 14:31, Liam O'Toole wrote:
>>>> On 2010-04-03, Ron Johnson <firstname.lastname@example.org> wrote:
>>>>> root@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 packages if necessary.
>>> (server)# grep ^BrowseAddress /etc/cups/cupsd.conf
>>> BrowseAddress @IF(eth0)
>>> Yes, I restarted cups after the change
>>> Client nmap output:
>>> (client)# nmap -p 631 haggis
>>> Starting Nmap 5.00 ( http://nmap.org ) at 2010-04-03 14:36 CDT
>>> Interesting ports on haggis.homelan (192.168.1.10):
>>> PORT STATE SERVICE
>>> 631/tcp closed ipp
>>> MAC Address: 00:24:1D:27:C0:FF (Giga-byte Technology Co.)
>>> Nmap done: 1 IP address (1 host up) scanned in 0.59 seconds
>> So cups simply isn't listening on eth0. What is the value of the Listen
>> variable in /etc/cups/cups.conf on the server?
> Do you really mean /etc/cups/cupsd.conf ?
Yes. Well spotted.
> # grep -n ^Listen /etc/cups/cupsd.conf
> 4:Listen localhost:631
> 5:Listen /var/run/cups/cups.sock
> Does "listen", in this case, also mean "listen for *requests* from
Yes, it specifies the interface(s) the daemon will bind to in order to
receive requests from clients.
Birmingham, United Kingdom