[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: accessing shared printed from virtualbox client [SOLVED]



On 2011-04-03, Steve Kleene <skdeb@syrano.acb.uc.edu> wrote:
--- SNIP ---
> I have some other notes.  On Sun, 3 Apr 2011 09:05:29 +0000 (UTC), Liam
> O'Toole had suggested:
>
>> To work around the problem above, tell CUPS to listen on the external
>> network interface as well:
>>
>>       Listen *:631
>
> Putting this line literally into cupsd.conf gave these errors in the log:
>
> E [03/Apr/2011:08:58:03 -0400] Unable to bind socket for address 0.0.0.0:631 -
> Address already in use.
> E [03/Apr/2011:08:58:03 -0400] Unable to bind socket for address :::631 -
> Address already in use.

I suspect that is because you kept the line

	Listen localhost:631

in the file as well. Once the daemon had bound to localhost it was
subsequently unable to bind to all interfaces --- because that would
require binding to localhost again!

>
> I also tried
>
>   Listen 192.168.1.*:631
>
> which gave
>
> E [03/Apr/2011:08:59:49 -0400] Hostname lookup for "192.168.1.*" failed!
> E [03/Apr/2011:08:59:49 -0400] Bad Listen address 192.168.1.*:631 at line 21.
>
> but either of these worked:
>
>   Listen 192.168.1.2:631
>   Listen drx:631
>
> I chose the second because I will only need to change hosts, and not
> cupsd.conf, on occasions when the router goes out and the host (drx) ends up
> with a new IP address.  I guess I'll still have to redefine the client
> printer's URL.

Some routers allow you to reserve an IP address for a particular client.
Another approach is to set up dnsmasq on your network and arrange your
own local DNS. But that is perhaps overkill for a small network.

>
> One oddity is that the XP client did nothing (appearing to hang) for 2-3 min
> after I entered the printer URL.  But then it came to life, and there is no
> delay when printing.
>
> Thanks much to both of you for your time and expertise.  I would not have
> figured this all out on my own.
>
>

You're welcome. I'm glad it's working now.

-- 
Liam O'Toole
Cork, Ireland


Reply to: