[Samba] Printer Rights Fail

[Van Sickler, Jim]

The samba docs/folks can tell you more about what spoolss
does... Disabling it reverts samba's printing to the
LanMan Server-mode printing.  That requires the driver
being installed on each PC (use client driver=yes).

The XP systems may have to have the printer reinstalled
using the Add Printer Wizard, and browse to the samba
server to select the printer.  Then use the XP driver
or "have Disk" method to install the driver.

As for the other (non-functioning) printer on the XP
systems, you might try adding a local port, type
Standard TCP/IP Port, and point it at the lpr port on
your samba server.

For my Lanier 2138, 2138 at samba1, the settings are:

Port Name:  2138
Printer Name or IP Address:  samba1
Protocol:  LPR
LPR Byte Counting Enabled = checked
SNMP Status Enabled = unchecked
--------------------------------------------------------

Two bonuses from using the LPR port instead of samba:
1.  I get the actual job name, not smbprn.xxxxxx.xxxxxx
2.  The Lanier Job History reflects the correct info as well.
Otherwise it displays "smbprn.xxxxxx.xxxxxx" or "Remote
Downlevel Document" as the file name, depending on how you
tweak the "print command =" entry in smb.conf.

I've sent several msgs to this list about how can I fix this...
Samba's using the spool dir file name as the job name, not
the PC-provided filename.  That's why it's smbprn.xxxxxx.xxxxxx,
and samba provides this to LPR/LPRng as the Job Name (%J).
If you print directly to LPR/LPRng, the correct file name
is displayed as the Job name.

Hope this helps,
  Jim



> -----Original Message-----
> From: Kevin Bramblett [mailto:kbramblett at dssresearch.com]
> Sent: Thursday, March 20, 2003 9:14 AM
> To: vansickj-eodc at Kaman.com
> Subject: RE: [Samba] Printer Rights Fail
> 
> 
> Jim,
> 
> Thanks for your help.  It corrected the immediate problem.  However, I
> noticed that for some XP systems we had using the lp printing 
> (apparently
> was using the spooler, I assume) stopped working.
> 
> Do you have any idea what the disable spoolss does?  We had 
> the use client
> driver already.
> 
> Thanks again for your help.
> 
> Kevin Bramblett
> 
> 
> Date: Wed, 19 Mar 2003 17:17:08 -0500
> From: "Van Sickler, Jim" <vansickj-eodc at Kaman.com>
> To: "Samba-L (E-mail)" <samba at lists.samba.org>
> Subject: RE: [Samba] Printer Rights Fail
> Message-ID: <D193D62C43BBD411A3690000F8F6943209F6EDE8 at ESKAC1>
> Content-Type: text/plain; charset=iso-8859-1
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7BIT
> Precedence: list
> Message: 45
> 
> add the following to your smb.conf [Global]:
> 
> disable spoolss = yes
> use client driver = yes
> 
> restart samba
> 
> Jim
> 
> > -----Original Message-----
> > From: Kevin Bramblett [mailto:kbramblett at dssresearch.com]
> > Sent: Wednesday, March 19, 2003 11:42 AM
> > To: samba at lists.samba.org
> > Subject: [Samba] Printer Rights Fail
> >
> >
> > Hello everyone,
> >
> > I upgraded my Samba server on my RHL 7.2 box from 2.2.3a to
> > 2.2.7.  Almost
> > immediately afterwards, all of my admin users suddenly were
> > unable to access
> > the printers that were being shared by Samba.  Any idea of
> > what is wrong and
> > how to fix it?  The messages I'm getting are that I do not 
> have enough
> > rights.
> >
> > I am using a Windows 2000 Server PDC and a lot of Windows 
> XP Pro, and
> > Windows 98/95 clients, of which the Win9x pcs and some XP
> > clients have no
> > problems.  Things are getting frantic here.
> >
> > Here is a copy of a portion of my smb.conf file for the printers:
> >
> > [global]
> >             printcap name = /etc/printcap
> >             load printers = yes
> >             printing = lprng
> >             use client driver = yes
> >
> > [printers]
> >             comment = All Printers
> >             path = /usr/spool/samba
> >             browseable = yes
> >             print command = lpr -b -r -h -P%p %s
> >             writeable = no
> >             printable = yes
> >             valid users = @DDS+"DOMAIN USERS" @DDS+"DOMAIN WEBUSERS"
> >
> > All help is appreciated.
> >
> > Thanks,
> > Kevin Bramblett
> > Network Administrator
> > DSS Research
> >
> > No trees were killed in the sending of this message.  However
> > a large number
> > of electrons were terribly inconvenienced.
>