[global]
print admin = @users
# shares
[HP_LaserJet_4000]
comment = Main Printer
path = /var/spool/lpd/HP_LaserJet_4000
guest ok = yes
public = yes
printer = HP_LaserJet_4000
;printing = bsd
printable = yes
browsable = yes
print command = /usr/bin/lpr -P%p %s && rm %s
lpq command = /usr/bin/lpq -P%p
lprm command = /usr/bin/lprm -P%p %j
[HP_LaserJet_6P]
comment = Front Desk Printer
path = /var/spool/lpd/HP_LaserJet_6P
guest ok = yes
public = yes
printer = HP_LaserJet_6P
;printing = bsd
printable = yes
browsable = yes
print command = /usr/bin/lpr -P%p %s && rm %s
lpq command = /usr/bin/lpq -P%p
lprm command = /usr/bin/lprm -P%p %j
Any advice would be greatly appreciated :)
Aaron Matlock wrote:
use client driver (S)
This parameter applies only to Windows NT/2000 clients. It has no affect on
Windows 95/98/ME clients. When serving a printer to Windows NT/2000 clients
without first installing a valid printer driver on the Samba host, the
client will be required to install a local printer driver. From this point
on, the client will treat the print as a local printer and not a network
printer connection. This is much the same behavior that will occur when
disable spoolss = yes.
The differentiating factor is that under normal circumstances, the NT/2000
client will attempt to open the network printer using MS-RPC. The problem is
that because the client considers the printer to be local, it will attempt
to issue the OpenPrinterEx() call requesting access rights associated with
the logged on user. If the user possesses local administator rights but not
root privilegde on the Samba host (often the case), the OpenPrinterEx() call
will fail. The result is that the client will now display an "Access Denied;
Unable to connect" message in the printer queue window (even though jobs may
successfully be printed).
----- Original Message -----
From: "Nick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 29, 2002 3:48 PM
Subject: [Samba] Printing Status - Access denied, unable to connect
Hi,
I have Samba 2.2.3a setup on a RH Linux 2.4.18-10 box as a print server.
It works fine, well kind of. The users can print their documents but on
their end the get the good old "Access Denied, unable to connect" error.
It does not seem to have any effect on the actual printing but its sucks
not being able to cancel a job. Anyone know if it is possible to not get
this error and be able to cancel jobs from the client machine?
Thanks,
Nick
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
