I have Samba 2.2.8a on my Red Hat 9 as the Primary
Domain Controller. 
 
I can print everything pretty well from my Red Hat 9
box. 
 
I can logon to Samba-controlled domain METRAN from my
XP boxes, and I can also 
see the shared printer - smbLPR, which is a HP
LaserJet 4si.  But the status 
of the shared printer is "Access denied, unable to
connect". 
 
If I double click it, XP says: 
 
A policy is in effect on your computer which prevents
you from connecting to 
this print queue. Please contact your system
administrator. 
 
I followed the instructions at
http://support.microsoft.com/?kbid=319939 and 
enabled point and print.  But the problem remains. 
 
Here is the part of my smb.conf which has to do with
the printer setting.  
Please note that I have to use lpr.cups on my Red Hat
system to print 
anything. lpr does not work. 
 
[smbLPR] 
        path = /var/tmp 
        printable = Yes 
        printing = bsd 
        print command = lpr.cups -P%p -r %s 
        printer name = mySambaPrinter 
 
Any idea on how to fix this?
Aschaffer@bloomberg.com
2003-Sep-22  23:06 UTC
[Samba] Samba printer: Access denied, unable to connect
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Please post the global section of smb.conf
do you have use client drivers = yes ?  I have seen that cause this
problem a number of times
- -----Original Message-----
From: Mark Liu [mailto:markliu1989@YAHOO.COM]
Sent: Monday, September 22, 2003 8:54 AM
To: samba
Subject: [Samba] Samba printer: Access denied, unable to connect
I have Samba 2.2.8a on my Red Hat 9 as the Primary
Domain Controller. 
 
I can print everything pretty well from my Red Hat 9
box. 
 
I can logon to Samba-controlled domain METRAN from my
XP boxes, and I can also 
see the shared printer - smbLPR, which is a HP
LaserJet 4si.  But the status 
of the shared printer is "Access denied, unable to
connect". 
 
If I double click it, XP says: 
 
A policy is in effect on your computer which prevents
you from connecting to 
this print queue. Please contact your system
administrator. 
 
I followed the instructions at
http://support.microsoft.com/?kbid=319939 and 
enabled point and print.  But the problem remains. 
 
Here is the part of my smb.conf which has to do with
the printer setting.  
Please note that I have to use lpr.cups on my Red Hat
system to print 
anything. lpr does not work. 
 
[smbLPR] 
        path = /var/tmp 
        printable = Yes 
        printing = bsd 
        print command = lpr.cups -P%p -r %s 
        printer name = mySambaPrinter 
 
Any idea on how to fix this? 
 
 
- -- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBP2+Aiyh4imLwvL+vEQJuKgCfQnnqUo0dse3usNlcIw37dGsJhAAAnRsA
tsrkOHGa6vnDMMR2v8xIabKz
=8IoK
-----END PGP SIGNATURE-----
Hi there, in my opinion you have to set the parameter. printing = cups and not = bsd, hope it helps. CU Ben Am Mon, 2003-09-22 um 17.54 schrieb Mark Liu:> I have Samba 2.2.8a on my Red Hat 9 as the Primary > Domain Controller. > > I can print everything pretty well from my Red Hat 9 > box. > > I can logon to Samba-controlled domain METRAN from my > XP boxes, and I can also > see the shared printer - smbLPR, which is a HP > LaserJet 4si. But the status > of the shared printer is "Access denied, unable to > connect". > > If I double click it, XP says: > > A policy is in effect on your computer which prevents > you from connecting to > this print queue. Please contact your system > administrator. > > I followed the instructions at > http://support.microsoft.com/?kbid=319939 and > enabled point and print. But the problem remains. > > Here is the part of my smb.conf which has to do with > the printer setting. > Please note that I have to use lpr.cups on my Red Hat > system to print > anything. lpr does not work. > > [smbLPR] > path = /var/tmp > printable = Yes > printing = bsd > print command = lpr.cups -P%p -r %s > printer name = mySambaPrinter > > Any idea on how to fix this? > > >