Hi,
I just installed 2 Win2K sp4 workstations on an otherwise working Samba 2.2.8a
network and 2 of the 3 printers are showing "Access denied".
What's up with that?
The other computers that are working just fine are Win98, XP and Win2K NOT sp4.
Here is part of the global section:
printing = bsd
load printers = yes
disable spoolss = yes
printcap name = /etc/printcap
printer admin = admin, administrator, @ntadmin
Here is one of the printers:
[Printer]
comment = Our Printer
path = /var/spool/lpd/hp4000n
queuepause command = /usr/sbin/lpc -P%p stop
queueresume command = /usr/sbin/lpc -P%p start
print command = /usr/bin/lpr -Php4000n -r %s
use client driver = yes
printer name = hp4000n
browsable = yes
printable = yes
guest ok = yes
writable = no
public = yes
force user = lp
create mask = 0700
write list = admin, administrator, @ntadmin
All the printers are identical except for the name and the path. They work for
everybody except the Win2K sp4.
Any ideas?
Thanks
--
Bob Crandell
Assured Computing
When you need to be sure.
bob@assuredcomp.com
www.assuredcomp.com
Voice - 541-689-9159
FAX - 541-463-1627
Eugene, Oregon
Check to see if they can still print. Win2K does that to me too, but they can still print. I had to add: use client driver = yes To the printers defenition to get the Access Denied error to go away. HTH Rick Bob Crandell wrote:>Hi, > >I just installed 2 Win2K sp4 workstations on an otherwise working Samba 2.2.8a >network and 2 of the 3 printers are showing "Access denied". What's up with that? >The other computers that are working just fine are Win98, XP and Win2K NOT sp4. > >Here is part of the global section: > printing = bsd > load printers = yes > disable spoolss = yes > printcap name = /etc/printcap > printer admin = admin, administrator, @ntadmin > >Here is one of the printers: >[Printer] > comment = Our Printer > path = /var/spool/lpd/hp4000n > queuepause command = /usr/sbin/lpc -P%p stop > queueresume command = /usr/sbin/lpc -P%p start > print command = /usr/bin/lpr -Php4000n -r %s > use client driver = yes > printer name = hp4000n > browsable = yes > printable = yes > guest ok = yes > writable = no > public = yes > force user = lp > create mask = 0700 > write list = admin, administrator, @ntadmin > >All the printers are identical except for the name and the path. They work for >everybody except the Win2K sp4. > >Any ideas? > >Thanks > >-- >Bob Crandell >Assured Computing >When you need to be sure. >bob@assuredcomp.com >www.assuredcomp.com >Voice - 541-689-9159 >FAX - 541-463-1627 >Eugene, Oregon > > > >
I already have "use client driver = yes". They can't print. What is sp4 doing that is getting in the way? Is there a registry hack to fix it? Thanks D. Rick Anderson (ruger@acsnv.com) wrote:> >Check to see if they can still print. Win2K does that to me too, but >they can still print. I had to add: > >use client driver = yes > >To the printers defenition to get the Access Denied error to go away. > >HTH > >Rick > >Bob Crandell wrote: > >>Hi, >> >>I just installed 2 Win2K sp4 workstations on an otherwise working Samba 2.2.8a >>network and 2 of the 3 printers are showing "Access denied". What's up with that? >>The other computers that are working just fine are Win98, XP and Win2K NOT sp4. >> >>Here is part of the global section: >> printing = bsd >> load printers = yes >> disable spoolss = yes >> printcap name = /etc/printcap >> printer admin = admin, administrator, @ntadmin >> >>Here is one of the printers: >>[Printer] >> comment = Our Printer >> path = /var/spool/lpd/hp4000n >> queuepause command = /usr/sbin/lpc -P%p stop >> queueresume command = /usr/sbin/lpc -P%p start >> print command = /usr/bin/lpr -Php4000n -r %s >> use client driver = yes >> printer name = hp4000n >> browsable = yes >> printable = yes >> guest ok = yes >> writable = no >> public = yes >> force user = lp >> create mask = 0700 >> write list = admin, administrator, @ntadmin >> >>All the printers are identical except for the name and the path. They work for >>everybody except the Win2K sp4. >> >>Any ideas? >> >>Thanks >> >>-- >>Bob Crandell >>Assured Computing >>When you need to be sure. >>bob@assuredcomp.com >>www.assuredcomp.com >>Voice - 541-689-9159 >>FAX - 541-463-1627 >>Eugene, Oregon >> >> >> >> > > >-- Bob Crandell Assured Computing When you need to be sure. bob@assuredcomp.com www.assuredcomp.com Voice - 541-689-9159 FAX - 541-463-1627 Eugene, Oregon
Bob,
Are the units printing? The access denied is on my win2k SP2 and it
is still printing. Why did you use printing = bsd? I used cups, and
it is working. Also there are two files mime.types, and mime.conv
that might need to be changed. (SAMBA DIR)
Steven
-----Original Message-----
From: samba-bounces+spierce=page-developer.net@lists.samba.org
[mailto:samba-bounces+spierce=page-developer.net@lists.samba.org]On
Behalf Of Bob Crandell
Sent: Thursday, July 17, 2003 8:52 AM
To: Samba List
Subject: [Samba] Win2K sp4 can't print
Hi,
I just installed 2 Win2K sp4 workstations on an otherwise working Samba
2.2.8a
network and 2 of the 3 printers are showing "Access denied".
What's up with
that?
The other computers that are working just fine are Win98, XP and Win2K NOT
sp4.
Here is part of the global section:
printing = bsd
load printers = yes
disable spoolss = yes
printcap name = /etc/printcap
printer admin = admin, administrator, @ntadmin
Here is one of the printers:
[Printer]
comment = Our Printer
path = /var/spool/lpd/hp4000n
queuepause command = /usr/sbin/lpc -P%p stop
queueresume command = /usr/sbin/lpc -P%p start
print command = /usr/bin/lpr -Php4000n -r %s
use client driver = yes
printer name = hp4000n
browsable = yes
printable = yes
guest ok = yes
writable = no
public = yes
force user = lp
create mask = 0700
write list = admin, administrator, @ntadmin
All the printers are identical except for the name and the path. They work
for
everybody except the Win2K sp4.
Any ideas?
Thanks
--
Bob Crandell
Assured Computing
When you need to be sure.
bob@assuredcomp.com
www.assuredcomp.com
Voice - 541-689-9159
FAX - 541-463-1627
Eugene, Oregon
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
There have been a number of issues with SP4. We always recommend that people test patches (especially Microsoft's) in a lab before deploying. Here is a link: http://www.winnetmag.com/Articles/Index.cfm?ArticleID=39584 "Bob Crandell" <bob@assuredcomp.com> wrote in message news:20030717.t3g.58456400@ocicat.crandell.net...> Hi, > > I just installed 2 Win2K sp4 workstations on an otherwise working Samba2.2.8a> network and 2 of the 3 printers are showing "Access denied". What's upwith that?> The other computers that are working just fine are Win98, XP and Win2K NOTsp4.> > Here is part of the global section: > printing = bsd > load printers = yes > disable spoolss = yes > printcap name = /etc/printcap > printer admin = admin, administrator, @ntadmin > > Here is one of the printers: > [Printer] > comment = Our Printer > path = /var/spool/lpd/hp4000n > queuepause command = /usr/sbin/lpc -P%p stop > queueresume command = /usr/sbin/lpc -P%p start > print command = /usr/bin/lpr -Php4000n -r %s > use client driver = yes > printer name = hp4000n > browsable = yes > printable = yes > guest ok = yes > writable = no > public = yes > force user = lp > create mask = 0700 > write list = admin, administrator, @ntadmin > > All the printers are identical except for the name and the path. Theywork for> everybody except the Win2K sp4. > > Any ideas? > > Thanks > > -- > Bob Crandell > Assured Computing > When you need to be sure. > bob@assuredcomp.com > www.assuredcomp.com > Voice - 541-689-9159 > FAX - 541-463-1627 > Eugene, Oregon > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Bob,
I've upgraded several systems here to SP4,
and haven't run into any of these errors (yet!).
However...
Spoolss was updated in SP4; I'd try deleting
the printers & their ports on the SP4 PCs, then
adding them again. If you toggled or added the
"disable spoolss = yes" setting, or upgraded
to 2.2.8a after the ports on the win2k PCs
were created, it may cause the "Access Denied" error.
Are you setting the printers up as Network or
Local on the PCs? It makes a difference. Local gave
me fewer problems. Use \\server\printshare as the
port name.
The lpc commands don't look quite right -
mine are from lprng, but the syntax is pretty
much the same:
lpq command = /usr/local/bin/lpstat %p
lprm command = /usr/local/bin/lprm -P%p %j
lppause command = /usr/local/sbin/lpc hold %p %j
lpresume command = /usr/local/sbin/lpc release %p %j
queuepause command = /usr/local/sbin/lpc stop %p
queueresume command = /usr/local/sbin/lpc start %p
To be honest, I've pretty much given up on printing in
Samba 2.x, and gone over to Standard TCP/IP Ports, printing
to the lprng daemon on the Samba server. I posted a whole
bunch of times trying to get a way to enumerate the correct
print job info on the clients, instead of the smbprn.xxx.xxx
that is usually available. I never got a solution...
Printing through lprng has given me two big benefits:
my Lanier 2138 no longer goes off into la-la land
(don't get me started on Ricoh's COMPLETELY CRAPPY job
of de-bugging their firmware), and the correct info is displayed
for the printer queues.
Hope this helps,
Jim
> -----Original Message----- > From: Chuck Stuettgen [mailto:cstuettgen@myrealbox.com] > Sent: Wednesday, July 23, 2003 9:22 PM > To: Van Sickler, Jim > Subject: RE: [Samba] Win2K sp4 can't print > > > On Wed, 2003-07-23 at 21:32, Van Sickler, Jim wrote: > > Bob, > > > > I've upgraded several systems here to SP4, > > and haven't run into any of these errors (yet!). > > > > However... > > > > Spoolss was updated in SP4; I'd try deleting > > the printers & their ports on the SP4 PCs, then > > adding them again. If you toggled or added the > > "disable spoolss = yes" setting, or upgraded > > to 2.2.8a after the ports on the win2k PCs > > were created, it may cause the "Access Denied" error. > > "disable spoolss = yes" didn't fix the "Access Denied" error for my > w2ksp3 clients. (haven't tried sp4 yet) > > "use client driver = yes" gets rid of the "Access Denied" error but I > now get "....error opening, retrying" message and the print > jobs are not > displayed in the print queue. But, I'm still working it.. > > > Are you setting the printers up as Network or > > Local on the PCs? It makes a difference. Local gave > > me fewer problems. Use \\server\printshare as the > > port name. > > Could you tell me how you set a UNC as a port without using > the Network > option in the printer setup wizard? > > How do you add it as new port?Start, Settings, Printers, Add Printer, Local Printer, Next, Create a New Port; Type: Local Port, enter the UNC for the Samba share as the Port Name. Done! NOTE: The share has to exist in order to add it. You'll get a "Not Found" error if it doesn't.> > > To be honest, I've pretty much given up on printing in > > Samba 2.x, and gone over to Standard TCP/IP Ports, printing > > to the lprng daemon on the Samba server. I posted a whole > > bunch of times trying to get a way to enumerate the correct > > print job info on the clients, instead of the smbprn.xxx.xxx > > that is usually available. I never got a solution... > > > > I'm using the stock RH 8.0 Samba 2.2.5-10 and LPRng 3.8.9-6. > > It took me a few days of google searches before I finally found this.. > > Add the -U%U -J"%J" parameters to get lpq to display the document name > instead of smbprn.xxxxxx.xxxxx. This works for both W2k and W9x > clients. The quotes around the %J are required. > > Mine looks like this: > > print command = lpr -P%p -U%U -J"%J" -r %s >I'll give that a try and see what's displayed.> Be aware of one oddity, on our w2k clients with the Novell Netware > client installed, if the user is logged in the local > workstation account > as administrator and the Novell account as his regular account, print > jobs will show up with the name as "Remote Download Document" > instead of > the real document name. If you create a local workstation account that > matches the Novell user account and have the user use that > instead, then > the print jobs will display the correct document name.All of my users are admin's on their PCs, and log onto the PC with their Domain user account. They also display "Remote Downlevel Document" instead of the file name. No Novell client installed. No local accounts.> > I haven't done any further testing of this, we don't have a Windows > domain and I haven't tried removing the Novell client and > printing so I > don't know if it Microsoft or Novell bug. > > -- > Like the dinosaur, Windows on the desktop is destined to > become extinct... > > Chuck Stuettgen cstuettgen@myrealbox.com > http://www.cfs-tech.homelinux.net >
Van, I think part of it was my fault. I went back and looked at some of the other NT4, XP and Win2K that were working fine and found out that they were all setup as local printers, that is, captured LPT ports. I don't think I can blame sp4. I wish I couldn't blame me. Thanks Van Sickler, Jim (vansickj-eodc@kaman.com) wrote:> >Bob, > > I've upgraded several systems here to SP4, >and haven't run into any of these errors (yet!). > >However... > > Spoolss was updated in SP4; I'd try deleting >the printers & their ports on the SP4 PCs, then >adding them again. If you toggled or added the >"disable spoolss = yes" setting, or upgraded >to 2.2.8a after the ports on the win2k PCs >were created, it may cause the "Access Denied" error. > > Are you setting the printers up as Network or >Local on the PCs? It makes a difference. Local gave >me fewer problems. Use \\server\printshare as the >port name. > > The lpc commands don't look quite right - >mine are from lprng, but the syntax is pretty >much the same: > > lpq command = /usr/local/bin/lpstat %p > lprm command = /usr/local/bin/lprm -P%p %j > lppause command = /usr/local/sbin/lpc hold %p %j > lpresume command = /usr/local/sbin/lpc release %p %j > queuepause command = /usr/local/sbin/lpc stop %p > queueresume command = /usr/local/sbin/lpc start %p > > To be honest, I've pretty much given up on printing in >Samba 2.x, and gone over to Standard TCP/IP Ports, printing >to the lprng daemon on the Samba server. I posted a whole >bunch of times trying to get a way to enumerate the correct >print job info on the clients, instead of the smbprn.xxx.xxx >that is usually available. I never got a solution... > > Printing through lprng has given me two big benefits: >my Lanier 2138 no longer goes off into la-la land >(don't get me started on Ricoh's COMPLETELY CRAPPY job >of de-bugging their firmware), and the correct info is displayed >for the printer queues. > >Hope this helps, >Jim >-- Bob Crandell Assured Computing When you need to be sure. bob@assuredcomp.com www.assuredcomp.com Voice - 541-689-9159 FAX - 541-463-1627 Eugene, Oregon
You can blame SP4 if you want too; I won't mind. Weren't those PCs printing ok prior to the upgrade to SP4? Honestly, I've only had one of about 1/2 dozen PCs that I've put SP4 on show any oddities aftewards. And the one PC was flaky prior to the SP install. The SP4 folks here that are using Solidworks 2003 have noticed their systems are much more stable, and what used to be BSODs are now CTDs (Crash To Desktops) instead. Solidworks crashing now only kills itself, instead of the whole system... Jim> -----Original Message----- > From: Bob Crandell [mailto:bob@assuredcomp.com] > Sent: Thursday, July 24, 2003 10:06 AM > To: Samba List > Subject: RE: [Samba] Win2K sp4 can't print > > > Van, > > I think part of it was my fault. I went back and looked at > some of the other NT4, > XP and Win2K that were working fine and found out that they > were all setup as local > printers, that is, captured LPT ports. I don't think I can > blame sp4. I wish I > couldn't blame me. > > Thanks > > > Van Sickler, Jim (vansickj-eodc@kaman.com) wrote: > > > >Bob, > > > > I've upgraded several systems here to SP4, > >and haven't run into any of these errors (yet!). > > > >However... > > > > Spoolss was updated in SP4; I'd try deleting > >the printers & their ports on the SP4 PCs, then > >adding them again. If you toggled or added the > >"disable spoolss = yes" setting, or upgraded > >to 2.2.8a after the ports on the win2k PCs > >were created, it may cause the "Access Denied" error. > > > > Are you setting the printers up as Network or > >Local on the PCs? It makes a difference. Local gave > >me fewer problems. Use \\server\printshare as the > >port name. > > > > The lpc commands don't look quite right - > >mine are from lprng, but the syntax is pretty > >much the same: > > > > lpq command = /usr/local/bin/lpstat %p > > lprm command = /usr/local/bin/lprm -P%p %j > > lppause command = /usr/local/sbin/lpc hold %p %j > > lpresume command = /usr/local/sbin/lpc release %p %j > > queuepause command = /usr/local/sbin/lpc stop %p > > queueresume command = /usr/local/sbin/lpc start %p > > > > To be honest, I've pretty much given up on printing in > >Samba 2.x, and gone over to Standard TCP/IP Ports, printing > >to the lprng daemon on the Samba server. I posted a whole > >bunch of times trying to get a way to enumerate the correct > >print job info on the clients, instead of the smbprn.xxx.xxx > >that is usually available. I never got a solution... > > > > Printing through lprng has given me two big benefits: > >my Lanier 2138 no longer goes off into la-la land > >(don't get me started on Ricoh's COMPLETELY CRAPPY job > >of de-bugging their firmware), and the correct info is displayed > >for the printer queues. > > > >Hope this helps, > >Jim > > > > -- > Bob Crandell > Assured Computing > When you need to be sure. > bob@assuredcomp.com > www.assuredcomp.com > Voice - 541-689-9159 > FAX - 541-463-1627 > Eugene, Oregon > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Ok, thanks, I will. These were brand spanking new, fresh out of the box, never touched by human hands (sort of), computers. Thanks Van Sickler, Jim (vansickj-eodc@kaman.com) wrote:> >You can blame SP4 if you want too; I won't mind. > >Weren't those PCs printing ok prior to the >upgrade to SP4? > >Honestly, I've only had one of about >1/2 dozen PCs that I've put SP4 on show any >oddities aftewards. And the one PC was flaky >prior to the SP install. > >The SP4 folks here that are using Solidworks 2003 >have noticed their systems are much more stable, >and what used to be BSODs are now CTDs (Crash >To Desktops) instead. Solidworks crashing >now only kills itself, instead of the whole >system... > >Jim > >> -----Original Message----- >> From: Bob Crandell [mailto:bob@assuredcomp.com] >> Sent: Thursday, July 24, 2003 10:06 AM >> To: Samba List >> Subject: RE: [Samba] Win2K sp4 can't print >> >> >> Van, >> >> I think part of it was my fault. I went back and looked at >> some of the other NT4, >> XP and Win2K that were working fine and found out that they >> were all setup as local >> printers, that is, captured LPT ports. I don't think I can >> blame sp4. I wish I >> couldn't blame me. >> >> Thanks >> >> >> Van Sickler, Jim (vansickj-eodc@kaman.com) wrote: >> > >> >Bob, >> > >> > I've upgraded several systems here to SP4, >> >and haven't run into any of these errors (yet!). >> > >> >However... >> > >> > Spoolss was updated in SP4; I'd try deleting >> >the printers & their ports on the SP4 PCs, then >> >adding them again. If you toggled or added the >> >"disable spoolss = yes" setting, or upgraded >> >to 2.2.8a after the ports on the win2k PCs >> >were created, it may cause the "Access Denied" error. >> > >> > Are you setting the printers up as Network or >> >Local on the PCs? It makes a difference. Local gave >> >me fewer problems. Use \\server\printshare as the >> >port name. >> > >> > The lpc commands don't look quite right - >> >mine are from lprng, but the syntax is pretty >> >much the same: >> > >> > lpq command = /usr/local/bin/lpstat %p >> > lprm command = /usr/local/bin/lprm -P%p %j >> > lppause command = /usr/local/sbin/lpc hold %p %j >> > lpresume command = /usr/local/sbin/lpc release %p %j >> > queuepause command = /usr/local/sbin/lpc stop %p >> > queueresume command = /usr/local/sbin/lpc start %p >> > >> > To be honest, I've pretty much given up on printing in >> >Samba 2.x, and gone over to Standard TCP/IP Ports, printing >> >to the lprng daemon on the Samba server. I posted a whole >> >bunch of times trying to get a way to enumerate the correct >> >print job info on the clients, instead of the smbprn.xxx.xxx >> >that is usually available. I never got a solution... >> > >> > Printing through lprng has given me two big benefits: >> >my Lanier 2138 no longer goes off into la-la land >> >(don't get me started on Ricoh's COMPLETELY CRAPPY job >> >of de-bugging their firmware), and the correct info is displayed >> >for the printer queues. >> > >> >Hope this helps, >> >Jim >> > >> >> -- >> Bob Crandell >> Assured Computing >> When you need to be sure. >> bob@assuredcomp.com >> www.assuredcomp.com >> Voice - 541-689-9159 >> FAX - 541-463-1627 >> Eugene, Oregon >> >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: http://lists.samba.org/mailman/listinfo/samba >> >-- Bob Crandell Assured Computing When you need to be sure. bob@assuredcomp.com www.assuredcomp.com Voice - 541-689-9159 FAX - 541-463-1627 Eugene, Oregon