I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver built with --with-ldapsam. The clients are either win9x or WinY2k. Authenitcation, etc... all works great. But print sharing is a real pain. Under 2.2.1a printing worked great, but our VOIP phone system wouldn't joint the domain until we upgraded to 2.2.4. Initial testing of 2.2.4 made it seem like everything worked. But eventually WinY2k users can't print, they simply get access denied. If they remove the printer and re-add they can't print for a little while before it goes back to access denied. ANY assistance would be greatly appreciated.
I assume this sentence: re-add they can't print for a little while before really should be: re-add they can print for a little while before This sounds like authentication (how would I know). Have you tried easing up on the security, making the print share guest ok =yes. Joel On Thu, May 16, 2002 at 02:26:16PM -0400, adam@morrison-ind.com wrote:> I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver > built with --with-ldapsam. The clients are either win9x or WinY2k. > Authenitcation, etc... all works great. > > But print sharing is a real pain. Under 2.2.1a printing worked great, but our > VOIP phone system wouldn't joint the domain until we upgraded to 2.2.4. Initial > testing of 2.2.4 made it seem like everything worked. But eventually WinY2k > users can't print, they simply get access denied. If they remove the printer > and re-add they can't print for a little while before it goes back to access denied. > > ANY assistance would be greatly appreciated. > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
> -----Original Message----- > From: Adam Williams [mailto:adam@morrison-ind.com] > Sent: Friday, May 17, 2002 5:06 AM > To: Joel Hammer > Cc: samba@lists.samba.org > Subject: Re: [Samba] WinY2k Access Denied on Printing > > > >I assume this sentence: > >re-add they can't print for a little while before > >really should be: re-add they can print for a little while before > > Yes. > > >This sounds like authentication (how would I know). > > This identical config worked without this problem under Samba > 2.2.1a. If > it was authenitcation how would they be able to print at all? > It does > work, but only for awhile. > > >Have you tried easing up on the security, making the print > share guest ok =yes. > > Every printer queue stanza looks like this: > > [traps] > comment = Traverse City Optra Laser Printer > path = /tmp > create mask = 0700 > guest ok = Yes > printable = Yes1. I'd get rid of the create mask 2. Create /var/spool/samba/traps 3. chmod -R 01777 /var/spool/samba 4. chown -R root.wheel /var/spool/samba 5. set your [traps] path = /var/spool/samba/traps 6. create /var/spool/lpd/traps 7. in /etc/printcap, set traps' :sd=/var/spool/lpd/traps: Let us know what happens... Jim> > > >>I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 > PDC and fileserver > >>built with --with-ldapsam. The clients are either win9x or WinY2k. > >>Authenitcation, etc... all works great. > >>But print sharing is a real pain. Under 2.2.1a printing > worked great, but our > >>VOIP phone system wouldn't joint the domain until we > upgraded to 2.2.4. Initial > >>testing of 2.2.4 made it seem like everything worked. But > eventually WinY2k > >>users can't print, they simply get access denied. If they > remove the printer > >>and re-add they can't print for a little while before it > goes back to access denied. > >>ANY assistance would be greatly appreciated. > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Don't forget to restart your lpd & samba services before testing it... Jim
What is your printer admin set to ?? What is your security set to ?? I had a problem with 2.2.4 where anyone who fell into the category of printer admin was denied access to the properties of the printer BUT it only happened to w2k and xp, NT worked fine. I realize this isn't the same error but it's worth a try. Josh Konkol, CNE MCSE Senior Network Analyst GuideOne Insurance Mail Stop AB-1 515-267-2427 jkonkol@guidemail.com .~. /V\ /( )\ ^^-^^ -----Original Message----- From: Adam Williams [mailto:adam@morrison-ind.com] Sent: Friday, May 17, 2002 10:54 AM To: Van Sickler, Jim Cc: samba@lists.samba.org Subject: RE: [Samba] WinY2k Access Denied on Printing>>>I assume this sentence: >>>re-add they can't print for a little while before >>>really should be: re-add they can print for a little while before >>Yes. >>>This sounds like authentication (how would I know). >>This identical config worked without this problem under Samba >>2.2.1a. If it was authenitcation how would they be able to print at all?>>It does work, but only for awhile. >>>Have you tried easing up on the security, making the print >>share guest ok =yes. >>Every printer queue stanza looks like this: >> [traps] >> comment = Traverse City Optra Laser Printer >> path = /tmp >> create mask = 0700 >> guest ok = Yes >> printable = Yes > >1. I'd get rid of the create mask >2. Create /var/spool/samba/traps >3. chmod -R 01777 /var/spool/samba >4. chown -R root.wheel /var/spool/samba >5. set your [traps] path = /var/spool/samba/traps >6. create /var/spool/lpd/traps >7. in /etc/printcap, set traps' :sd=/var/spool/lpd/traps:Ok, i modified one of my queues - [grdps] comment = Grand Rapids Optra Laser Printer path = /var/spool/samba/grdps guest ok = Yes printable = Yes ls -l /var/spool/samba total 0 drwxrwxrwt 2 root wheel 6 May 17 11:42 grdps Restarted smbd, and it does the same thing. I really appreciate the help, but i think your missing some important facts - 1. UNIX printing works flawlessly (this box is an lpd server for lots of unix clients). 2. Samba printing from both Win9x and WinY2k worked flawlessly under 2.2.1a, for a long time. 3. Printing does work, but only for awhile. And ONLY WinY2k clients are effected, Win9x clients continue to print just fine -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
> -----Original Message----- > From: Adam Williams [mailto:adam@morrison-ind.com] > Sent: Friday, May 17, 2002 8:54 AM > To: Van Sickler, Jim > Cc: samba@lists.samba.org > Subject: RE: [Samba] WinY2k Access Denied on Printing > > > >>>I assume this sentence: > >>>re-add they can't print for a little while before > >>>really should be: re-add they can print for a little while before > >>Yes. > >>>This sounds like authentication (how would I know). > >>This identical config worked without this problem under Samba > >>2.2.1a. If it was authenitcation how would they be able > to print at all? > >>It does work, but only for awhile. > >>>Have you tried easing up on the security, making the print > >>share guest ok =yes. > >>Every printer queue stanza looks like this: > >> [traps] > >> comment = Traverse City Optra Laser Printer > >> path = /tmp > >> create mask = 0700 > >> guest ok = Yes > >> printable = Yes > > > >1. I'd get rid of the create mask > >2. Create /var/spool/samba/traps > >3. chmod -R 01777 /var/spool/samba > >4. chown -R root.wheel /var/spool/samba > >5. set your [traps] path = /var/spool/samba/traps > >6. create /var/spool/lpd/traps > >7. in /etc/printcap, set traps' :sd=/var/spool/lpd/traps: > > Ok, i modified one of my queues - > [grdps] > comment = Grand Rapids Optra Laser Printer > path = /var/spool/samba/grdps > guest ok = Yes > printable = Yes > > ls -l /var/spool/samba > total 0 > drwxrwxrwt 2 root wheel 6 May 17 11:42 grdps > > Restarted smbd, and it does the same thing. > > I really appreciate the help, but i think your missing some important > facts - > > 1. UNIX printing works flawlessly (this box is an lpd server > for lots of > unix clients). > 2. Samba printing from both Win9x and WinY2k worked flawlessly under > 2.2.1a, for a long time. > 3. Printing does work, but only for awhile. And ONLY WinY2k > clients are > effected, Win9x clients continue to print just fine >I did miss the important facts :-( Do you have "disable spoolss=no" in smb.conf? If so, try "=yes" That is particular to Win2k; Win9x clients aren't affected. Is it happening on all of your Win2k clients? Who, if anyone, is set up as "admin users=" or "printer admin="? If I'm set up as an admin user in smb.conf, with "disable spoolss=no", I get the "access denied" msg when I try to get the printer's properties; don't know how print jobs went...never got that far. What port does Win2k say the printer is attached to? If it started out on a 2.2.1a box, it may say "LanMan Printer Port". If you removed it and re-installed it with 2.2.4 as a "network printer" and "disable spoolss=no", it may say that it's a Local Port. Try setting "disable spoolss=yes" and see if it'll let you reconnect it to the LanMan Printer Port. I had to set "disable spoolss=yes" on my server, because of all the hassles it was causing when the printer was added as a "Network Printer"...never tried it as a "Local Printer" with "...=no". 1. Conflicts with members of "printer admins" and "admin users" - couldn't view printer properties 2. Printer installed under HKey_Current_User, not HKey_Local_Machine - If I logged into the PC as Administrator and installed the printer, it didn't show up when I logged in under my account 3. Couldn't modify printer settings (memory, device settings, etc.) 4. SIDS displayed under Security tab; not Domain\Domain Users, etc. 5. Could view Properties on samba printer icon under Printers-as long as the printer wasn't installed on my PC and 'admin users=" was rem'd out (I'm in the Wheel group) or @wheel and vansickj weren't present. 6. I couldn't install the AdobePS or LexMark drivers onto the samba server; they only install on the local PC. I did manage to install the HP drivers onto the samba server; even with "disable spoolss=yes" the drivers install onto the Win2k PCs just fine from the server now- a good thing...the only good thing, out of a lot of manhours :-( 6. Many other oddities which I can't specifially recall right now... but will torment me at night for some time to come, I'm sure! How it behaves with "disable spoolss=no" and the printer added to my system as a "Local Printer", I'll never know. I've put off too many other jobs while fighting with samba for the last several weeks. I've got to attend to them, and let someone else bloody their forehead for a while..... Jim
Adam, Just one more thing, and I'll go away, I promise! ;-) If you set "disable spoolss=no", then install all of the printer drivers you can, and set "disable spoolss=yes", you should be able to install the printers as Network Printers, (not Local, as I mentioned in the last post) connected to the LanMan Printer Port (as in 2.2.1a), but pull the drivers off of the samba server, from [print$]. It works like that for me; but with "=yes", the Printers icon doesn't appear. If I double-click on the samba shared printer icon, I can view the properties. I can list myself or @wheel in the admin users, printer admins, and write list now, without any "access Denied" issues.... So what? Enable spoolss support when you want to install printer drivers on the server, then disable it. Save you from going back to 2.2.1a, maybe. Jim
I having the same problem with a couple of W2K boxes on our network. The user could print for a bit, then get access denied messages. If we stopped and restarted the Samba daemons the user was able to print again - for a while. Sometimes removing and re-adding the printer would work, sometimes not. After we installed service pack 2 on the Windows 2000 computers the problem stopped. Do you have service packs 2 on your W2K machines? -Bob Martel ****************************************************************************** Speaking only for myself - CSU pays better people than me to speak for them. Bob Martel - System Administrator | I met someone who looks Maxine Goodman Levin College of Urban Affairs | a lot like you Cleveland State University | She does the things you do (216) 687-2214 | But she is an IBM bob@urban.csuohio.edu | -Jeff Lynne ******************************************************************************
Is this documented anywhere in layman's terms? (NT/2k considers a Printer Connection as a different thing that a local printer) 1. Which section of the registry is the proper location for each type of printer. 2. How to install a Printer Connection for all users on the PC (not just CurrentUser) 3. Advantages/disadvantages of both types when printing to network printers via samba, lpr, etc Jim> -----Original Message----- > From: Gerald Carter [mailto:jerry@samba.org] > Sent: Saturday, May 18, 2002 5:59 AM > To: Fabiano Mucillo - func > Cc: Adam Williams; samba@lists.samba.org > Subject: RE: [Samba] WinY2k Access Denied on Printing > > > On Fri, 17 May 2002, Fabiano Mucillo - func wrote: > > > > I understand (pretty much) what "disable spoolss" and > "use client driver" > > > does but what is the behaviour of the no/yes > configuration. It seems that > > > "use client driver=yes" implies "disable spoolss=no" > > > > I don't think so. I understood that if you use "use client > driver=yes" > > you'll continue using spoolss, but with > PRINTER_ACCESS_ADMINISTER right is > > mapped to PRINTER_ACCESS_USE instead. Thus allowing the > OpenPrinterEx() > > call to succeed. > > Correct. This broken behavior was observed on NT clients when using > SPOOLSS calls for printing but having the driver installed locally. > Remember that NT/2k considers a Printer Connection as a > different thing > that a local printer. > > > > > > cheers, jerry > --------------------------------------------------------------------- > Hewlett-Packard http://www.hp.com > SAMBA Team http://www.samba.org > -- http://www.plainjoe.org > "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 > --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
On Thu, 16 May 2002 adam@morrison-ind.com wrote:> I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver > built with --with-ldapsam. The clients are either win9x or WinY2k. > Authenitcation, etc... all works great. > > But print sharing is a real pain. Under 2.2.1a printing worked great, > but our VOIP phone system wouldn't joint the domain until we upgraded to > 2.2.4. Initial testing of 2.2.4 made it seem like everything worked. > But eventually WinY2k users can't print, they simply get access denied. > If they remove the printer and re-add they can't print for a little > while before it goes back to access denied.Please try the printing roll up patch posted at ftp://samba.org/pub/jerry/samba-2.2.4-patches/ cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--