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

Re: accessing shared printed from virtualbox client [SOLVED]



On Sat, 2 Apr 2011 20:33:25 +0000 (UTC), I wrote:
> I have a Wheezy host, an XP virtualbox client, and an old LaserJet 5MP
> configured with CUPS and connected by a parallel port.  How can I access this
> printer from the XP client?

Here finally is the minimal solution that worked.  Based on the suggestions
from Liam O'Toole and tv.debian@googlemail.com, I added this to cupsd.conf:

  <Location />
  Order Deny,Allow
  Deny From All
  Allow From 127.0.0.1
  Allow From localhost
  Allow From @LOCAL
  </Location>

I also added this:

  Listen drx:631

where drx maps to 192.168.1.2 (the host) in /etc/hosts.  In the XP client, I
defined a printer at this URL:

  http://192.168.1.2:631/printers/LaserJet_5MP

That's it.  It works now.

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 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.

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.


Reply to: