[Samba] printer drivers

[Van Sickler, Jim]

What happens when you run
testparm?  Do you see any
error messages?

> -----Original Message-----
> From: mark [mailto:mark at mebrosius.com]
> Sent: Monday, June 10, 2002 4:09 PM
> To: Alex Meaden
> Cc: samba at lists.samba.org
> Subject: Re: [Samba] printer drivers
> 
> 
> When I open the printer folder I see the printer there.  It is not 
> shaded (indicating that the printer is offline).  I can 
> actually see it 
> in Network Neighborhood.  If I use the the 720c drivers 
> provided by HP, 
> I get an error message stating:
> There was an error writing to \\server\printer for the 
> printer (driver):
> Your file waiting to be printed was deleted
> 
> I am trying the basic HP Deskjet driver now just to see what 
> happens.  
> 
> Mark
> 
> Alex Meaden wrote:
> 
> >----- Original Message -----
> >From: "mark" <mark at mebrosius.com>
> >To: "Alex Meaden" <alex at meaden.net>; <samba at lists.samba.org>
> >Sent: Tuesday, June 11, 2002 12:02 AM
> >Subject: Re: [Samba] printer drivers
> >
> >
> >  
> >
> >>Alex,
> >>Thank for your help but I still can't print.   Here is my 
> smb.conf file.
> >> My file sharing works but not my printer.  Can you see 
> what I'm doing
> >>wrong?
> >>    
> >>
> >
> >I'm not that you should have a "[Printer]" share in your 
> smb.conf. If you
> >open \\mark from a Windows PC, and then double-click the 
> Printers folder,
> >what if anything is listed?
> >
> >Alex.
> >
> >  
> >
> >>[global]
> >>        workgroup = K9PC
> >>        netbios name = MARK
> >>        server string = Samba Server %v
> >>        encrypt passwords = Yes
> >>        log file = /var/log/samba/log.%m
> >>        max log size = 50
> >>        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> >>        printcap name = lpstat

Should this be /etc/printcap or /usr/local/etc/printcap?
I'm not sure which one cups uses :-(

> >>        dns proxy = No
> >>        wins support = Yes
> >>        hosts allow = 127.0.0. 192.168.1.
> >>        printing = cups
> >>
> >>[homes]
> >>        comment = Home Directories
> >>        read only = No
> >>        browseable = No
> >>
> >>[printers]
> >>        comment = All Printers
> >>        path = /var/spool/samba
> >>        create mask = 0700
> >>        guest ok = Yes
> >>        printable = Yes
> >>        print command = lpr-cups -P %p -o raw %s -r   # using client
> >>side printer drivers.
> >>        lpq command = lpstat -o %p
> >>        lprm command = cancel %p-%j
> >>        browseable = No

I think the samba spool dir needs to be 777 or 1777
try #'ing this entry to see if it changes anything.

then:

chown root.daemon /var/spool/samba
chmod 777 /var/spool/samba

Come to think of it, if you have an entry for the
printer, you don't need the [printers]
entry.  Rename the [printers] section to [Printer],
and delete the other [Printer] entry.  Modify it
to read:

[Printer]
        comment = HP720C
        path = /var/spool/samba
        guest ok = Yes
        printable = Yes
        print command = lpr-cups -P %p -o raw %s -r
        # using client side printer drivers.
        lpq command = lpstat -o %p
        lprm command = cancel %p-%j
        browseable = No


What I think is happening is that you can see
the Printer share, but samba and cups aren't
talking correctly.  Samba spools the job, and
sends it to cups.  Each print process must be
working in order for the job to be processed.
Look at your printcap entry for the printer,
and make sure it matches what you have in the
smb.conf [Printer] and [Global] sections.

You may consider creating the printcap entry
as hp720 or something similar;  chances are
you're going to end up servicing more than
one printer via your server.  Create
/var/spool/samba/hp720 and make the
[Printer] section [HP720C].  Modify the
path=/var/spool/samba/hp720 as well.  As you
add more printers,  you'll be able to give them
names that match their model.  Printer, Printer2,
etc. will add confusion instead of clarity...

If the HP720C driver won't work, try the
HP550C driver.  It's what I have to use for our
networked OfficeJet 570, and HP mentions it as a
solution for other networked DeskJets.

Hope this helps,

Jim