>
> Any suggestions as how to give the Windows XP permissions to
> see and delete their own jobs?
This may depend on which printing system you have on the linux box. A lot
of people seem to be using cups, about which I know nothing.
I use lprng. There is a file called lpd.perms, which hangs ou
Paul,
Thanks for the pointer to the pdf. Trying to load up drivers using a
windows client has proven to be problematic (I think on the windows end
and I'm not windows savvy). I got a set of all the drivers off the PDC
and tried installing them as per page 175 of the pdf. Problem is that I
don't
Rob Tanner wrote on Thursday, 24 July 2003 6:24 a.m.:
> 1. When attempting to connect to the printer from a Windows box in
> the domain (the SAMBA server is simply a server that's a member of
> the domain, it is not the PDC) I get the message that the server does
> not have the appropriate driver a
Don't you have to set up your clients to talk to each of the ten printers?
Joel
On Wed, Jul 23, 2003 at 11:24:17AM -0700, Rob Tanner wrote:
> I am using SAMBA/Lprng to do printer accounting for charge-back. There
> are two technical issues I have not been able to resolve.
>
> 1. When attempting t
Try adding :
use client driver = yes
to your printer share.
Joel
On Wed, Jul 23, 2003 at 11:24:17AM -0700, Rob Tanner wrote:
> 2. Even though I can print to the SAMBA shared printer without any
> problem, the box that gives printer status claims that it cannot connect
> to the printer. What sett
I am using SAMBA/Lprng to do printer accounting for charge-back. There
are two technical issues I have not been able to resolve.
1. When attempting to connect to the printer from a Windows box in the
domain (the SAMBA server is simply a server that's a member of the domain,
it is not the PDC) I g
