Insufficient Permissions to Spool directory with Samba printer - SMB

This is a discussion on Insufficient Permissions to Spool directory with Samba printer - SMB ; Hi, I'm trying to share-out a printer via Samba 3 on Slackware 10, and Samba picks it up and it loads okay on Windows -- but when I try to print from Windows it errors. After looking in /var/log/samba at ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Insufficient Permissions to Spool directory with Samba printer

  1. Insufficient Permissions to Spool directory with Samba printer

    Hi,

    I'm trying to share-out a printer via Samba 3 on Slackware 10, and
    Samba picks it up and it loads okay on Windows -- but when I try to
    print from Windows it errors.

    After looking in /var/log/samba at the logs for my PC it shows the
    following:
    [2004/11/09 16:55:00, 0] printing/print_cups.c:cups_queue_get(854)
    Unable to connect to CUPS server localhost - Connection refused
    [2004/11/09 16:56:37, 0] printing/print_cups.c:cups_queue_get(854)
    Unable to connect to CUPS server localhost - Connection refused
    [2004/11/09 16:56:43, 0] printing/printing.crint_job_start(2022)
    print_job_start: insufficient permissions to open spool file
    /var/spool/lpd/webmasterptr/smbprn.00000010.OZzAHy.

    Here's my smb.conf file:

    [global]
    log file = /var/log/samba/%m.log
    name resolve order = wins hosts lmhosts bcast
    idmap gid = 10000-20000
    socket options = SO_SNDBUF=16384 SO_RCVBUF=16384
    wins server = 10.142.120.6
    domain master = False
    encrypt passwords = yes
    public = yes
    level2 oplocks = False
    oplocks = False
    netbios name = HOSER
    write cache size = 8388608
    server string = Samba Server
    winbind enum users = yes
    idmap uid = 10000-20000
    password server = *
    workgroup = NTDOMAIN
    os level = 10
    winbind enum groups = yes
    security = domain
    preferred master = no
    winbind separator = +
    log level = 1

    [WebmasterPTR]
    comment = Printer in My Office
    Printer Name = WebmasterPTR
    path = /var/spool/lpd/webmasterptr
    read only = yes
    printable = yes
    use client driver = Yes

    Any ideas?? What permissions do I need to setup to allow this to
    work, or do I have something setup incorrectly in my smb.conf file?

    Thanks for any advice or suggestions...

    Ringo

  2. Re: Insufficient Permissions to Spool directory with Samba printer

    rlangly@gmail.com (Ringo Langly) wrote in message news:<7d96e89e.0411091358.40184a84@posting.google.com>...
    > Hi,
    >
    > I'm trying to share-out a printer via Samba 3 on Slackware 10, and
    > Samba picks it up and it loads okay on Windows -- but when I try to
    > print from Windows it errors.
    >
    > After looking in /var/log/samba at the logs for my PC it shows the
    > following:
    > [2004/11/09 16:55:00, 0] printing/print_cups.c:cups_queue_get(854)
    > Unable to connect to CUPS server localhost - Connection refused
    > [2004/11/09 16:56:37, 0] printing/print_cups.c:cups_queue_get(854)
    > Unable to connect to CUPS server localhost - Connection refused
    > [2004/11/09 16:56:43, 0] printing/printing.crint_job_start(2022)
    > print_job_start: insufficient permissions to open spool file
    > /var/spool/lpd/webmasterptr/smbprn.00000010.OZzAHy.
    >
    > Here's my smb.conf file:
    >
    > [global]
    > log file = /var/log/samba/%m.log
    > name resolve order = wins hosts lmhosts bcast
    > idmap gid = 10000-20000
    > socket options = SO_SNDBUF=16384 SO_RCVBUF=16384
    > wins server = 10.142.120.6
    > domain master = False
    > encrypt passwords = yes
    > public = yes
    > level2 oplocks = False
    > oplocks = False
    > netbios name = HOSER
    > write cache size = 8388608
    > server string = Samba Server
    > winbind enum users = yes
    > idmap uid = 10000-20000
    > password server = *
    > workgroup = NTDOMAIN
    > os level = 10
    > winbind enum groups = yes
    > security = domain
    > preferred master = no
    > winbind separator = +
    > log level = 1
    >
    > [WebmasterPTR]
    > comment = Printer in My Office
    > Printer Name = WebmasterPTR
    > path = /var/spool/lpd/webmasterptr
    > read only = yes
    > printable = yes
    > use client driver = Yes
    >
    > Any ideas?? What permissions do I need to setup to allow this to
    > work, or do I have something setup incorrectly in my smb.conf file?
    >
    > Thanks for any advice or suggestions...
    >
    > Ringo


    Hi all,

    I have some additional information. After reading some docs I did
    find that I needed to change the path to something else, so I used
    /usr/spool/public and gave this directory 777 permissions. Now the
    printer installs fine on Windows and Windows shows it's printing fine
    -- problem is nothing prints.

    In /var/log/samba/ when trying to print I received this error:
    [2004/11/11 09:02:11, 0] printing/print_cups.c:cups_queue_get(854)
    Unable to connect to CUPS server localhost - Connection refused

    After doing a quick ps -aux | grep cupsd I found cups wasn't running,
    so I started cupsd. Now when I try to print I get this error:
    [2004/11/11 09:06:51, 0] printing/print_cups.c:cups_queue_get(911)
    Unable to get jobs for ipp://localhost/printers/webmasterptr -
    client-error-no
    t-found

    I'm totally lost now! This crap can't be this difficult! I've setup
    printers on samba before with little effort... but it just isn't
    working. The printer works fine via Linux and I can print a test page
    via webmin just fine.

    I know there's lpd and cups, which I was never sure the difference or
    which one was running at what time. Hmmm...

    Ringo -- scratching head...

  3. Re: Insufficient Permissions to Spool directory with Samba printer

    rlangly@gmail.com (Ringo Langly) wrote in message news:<7d96e89e.0411091358.40184a84@posting.google.com>...
    > Hi,
    >
    > I'm trying to share-out a printer via Samba 3 on Slackware 10, and
    > Samba picks it up and it loads okay on Windows -- but when I try to
    > print from Windows it errors.
    >
    > After looking in /var/log/samba at the logs for my PC it shows the
    > following:
    > [2004/11/09 16:55:00, 0] printing/print_cups.c:cups_queue_get(854)
    > Unable to connect to CUPS server localhost - Connection refused
    > [2004/11/09 16:56:37, 0] printing/print_cups.c:cups_queue_get(854)
    > Unable to connect to CUPS server localhost - Connection refused
    > [2004/11/09 16:56:43, 0] printing/printing.crint_job_start(2022)
    > print_job_start: insufficient permissions to open spool file
    > /var/spool/lpd/webmasterptr/smbprn.00000010.OZzAHy.
    >
    > Here's my smb.conf file:
    >
    > [global]
    > log file = /var/log/samba/%m.log
    > name resolve order = wins hosts lmhosts bcast
    > idmap gid = 10000-20000
    > socket options = SO_SNDBUF=16384 SO_RCVBUF=16384
    > wins server = 10.142.120.6
    > domain master = False
    > encrypt passwords = yes
    > public = yes
    > level2 oplocks = False
    > oplocks = False
    > netbios name = HOSER
    > write cache size = 8388608
    > server string = Samba Server
    > winbind enum users = yes
    > idmap uid = 10000-20000
    > password server = *
    > workgroup = NTDOMAIN
    > os level = 10
    > winbind enum groups = yes
    > security = domain
    > preferred master = no
    > winbind separator = +
    > log level = 1
    >
    > [WebmasterPTR]
    > comment = Printer in My Office
    > Printer Name = WebmasterPTR
    > path = /var/spool/lpd/webmasterptr
    > read only = yes
    > printable = yes
    > use client driver = Yes
    >
    > Any ideas?? What permissions do I need to setup to allow this to
    > work, or do I have something setup incorrectly in my smb.conf file?
    >
    > Thanks for any advice or suggestions...
    >
    > Ringo


    Second Update (incase Google gets them out of order)...

    I read in one post someone suggested adding "printing = bsd" to the
    mix, so here's my printer statement in smb.conf:

    [WebmasterPTR]
    Printer Name = webmasterptr
    path = /usr/spool/public
    read only = yes
    guest ok = yes
    printable = yes
    use client driver = Yes
    printing = bsd

    This did resolve the errors in Samba and when I print something the
    printer now flashes Processing Job for like 2 seconds and nothing ever
    prints. When I run lpq it shows a job just went through and printed
    fine -- but nothing printed.

    Any ideas?? As stated earlier I can print from Linux just fine via
    webmin and I'm testing from commandline now. Here's what lpc status
    shows:
    Printer Printing Spooling Jobs Server Subserver Redirect
    Status/(Debug)
    webmasterptr@hoser2 enabled enabled 0 none none

    Ideas???? Printer is an HP Laserjet 5N, nothing fancy.

    Ringo

  4. Re: Insufficient Permissions to Spool directory with Samba printer

    Can you print to the printer from the machine it's connected to? You
    might have a printer configuration issue. I fought with that same
    problem for a bit, and finally came to that conclusion. Got the
    printer set up right, and it started working. I had to use the CUPS
    drivers, though, as mine's a Lexmark Z42.

    HTH

    Ringo Langly wrote:
    > rlangly@gmail.com (Ringo Langly) wrote in message news:<7d96e89e.0411091358.40184a84@posting.google.com>...
    >
    >>Hi,
    >>
    >>I'm trying to share-out a printer via Samba 3 on Slackware 10, and
    >>Samba picks it up and it loads okay on Windows -- but when I try to
    >>print from Windows it errors.
    >>
    >>After looking in /var/log/samba at the logs for my PC it shows the
    >>following:
    >>[2004/11/09 16:55:00, 0] printing/print_cups.c:cups_queue_get(854)
    >> Unable to connect to CUPS server localhost - Connection refused
    >>[2004/11/09 16:56:37, 0] printing/print_cups.c:cups_queue_get(854)
    >> Unable to connect to CUPS server localhost - Connection refused
    >>[2004/11/09 16:56:43, 0] printing/printing.crint_job_start(2022)
    >> print_job_start: insufficient permissions to open spool file
    >>/var/spool/lpd/webmasterptr/smbprn.00000010.OZzAHy.
    >>
    >>Here's my smb.conf file:
    >>
    >>[global]
    >> log file = /var/log/samba/%m.log
    >> name resolve order = wins hosts lmhosts bcast
    >> idmap gid = 10000-20000
    >> socket options = SO_SNDBUF=16384 SO_RCVBUF=16384
    >> wins server = 10.142.120.6
    >> domain master = False
    >> encrypt passwords = yes
    >> public = yes
    >> level2 oplocks = False
    >> oplocks = False
    >> netbios name = HOSER
    >> write cache size = 8388608
    >> server string = Samba Server
    >> winbind enum users = yes
    >> idmap uid = 10000-20000
    >> password server = *
    >> workgroup = NTDOMAIN
    >> os level = 10
    >> winbind enum groups = yes
    >> security = domain
    >> preferred master = no
    >> winbind separator = +
    >> log level = 1
    >>
    >>[WebmasterPTR]
    >> comment = Printer in My Office
    >> Printer Name = WebmasterPTR
    >> path = /var/spool/lpd/webmasterptr
    >> read only = yes
    >> printable = yes
    >> use client driver = Yes
    >>
    >>Any ideas?? What permissions do I need to setup to allow this to
    >>work, or do I have something setup incorrectly in my smb.conf file?
    >>
    >>Thanks for any advice or suggestions...
    >>
    >>Ringo

    >
    >
    > Second Update (incase Google gets them out of order)...
    >
    > I read in one post someone suggested adding "printing = bsd" to the
    > mix, so here's my printer statement in smb.conf:
    >
    > [WebmasterPTR]
    > Printer Name = webmasterptr
    > path = /usr/spool/public
    > read only = yes
    > guest ok = yes
    > printable = yes
    > use client driver = Yes
    > printing = bsd
    >
    > This did resolve the errors in Samba and when I print something the
    > printer now flashes Processing Job for like 2 seconds and nothing ever
    > prints. When I run lpq it shows a job just went through and printed
    > fine -- but nothing printed.
    >
    > Any ideas?? As stated earlier I can print from Linux just fine via
    > webmin and I'm testing from commandline now. Here's what lpc status
    > shows:
    > Printer Printing Spooling Jobs Server Subserver Redirect
    > Status/(Debug)
    > webmasterptr@hoser2 enabled enabled 0 none none
    >
    > Ideas???? Printer is an HP Laserjet 5N, nothing fancy.
    >
    > Ringo



  5. Re: Insufficient Permissions to Spool directory with Samba printer

    > Second Update (incase Google gets them out of order)...
    >
    > I read in one post someone suggested adding "printing = bsd" to the
    > mix, so here's my printer statement in smb.conf:
    >
    > [WebmasterPTR]
    > Printer Name = webmasterptr
    > path = /usr/spool/public
    > read only = yes
    > guest ok = yes
    > printable = yes
    > use client driver = Yes
    > printing = bsd
    >
    > This did resolve the errors in Samba and when I print something the
    > printer now flashes Processing Job for like 2 seconds and nothing ever
    > prints. When I run lpq it shows a job just went through and printed
    > fine -- but nothing printed.
    >
    > Any ideas?? As stated earlier I can print from Linux just fine via
    > webmin and I'm testing from commandline now. Here's what lpc status
    > shows:
    > Printer Printing Spooling Jobs Server Subserver Redirect
    > Status/(Debug)
    > webmasterptr@hoser2 enabled enabled 0 none none
    >
    > Ideas???? Printer is an HP Laserjet 5N, nothing fancy.
    >
    > Ringo


    ok 2 things to try, edit the /etc/cups/mime.types and uncomment the last
    line that says

    application/octet-stream

    and then edit the mime.convs and also uncomment the last line showing

    application/octet-stream application/vnd.cups-raw 0 -

    then restart cups, then at the prompt type

    lpoptions -o raw

    then retry printing from your windows machine.

    If you are still getting premission errors, make sure your spool
    directory is writable by the guest account so it can spool the print job.

    See how you go with that

    Spyro

  6. Re: Insufficient Permissions to Spool directory with Samba printer

    Spyro Polymiadis wrote in message news:...
    > > Second Update (incase Google gets them out of order)...
    > >
    > > I read in one post someone suggested adding "printing = bsd" to the
    > > mix, so here's my printer statement in smb.conf:
    > >
    > > [WebmasterPTR]
    > > Printer Name = webmasterptr
    > > path = /usr/spool/public
    > > read only = yes
    > > guest ok = yes
    > > printable = yes
    > > use client driver = Yes
    > > printing = bsd
    > >
    > > This did resolve the errors in Samba and when I print something the
    > > printer now flashes Processing Job for like 2 seconds and nothing ever
    > > prints. When I run lpq it shows a job just went through and printed
    > > fine -- but nothing printed.
    > >
    > > Any ideas?? As stated earlier I can print from Linux just fine via
    > > webmin and I'm testing from commandline now. Here's what lpc status
    > > shows:
    > > Printer Printing Spooling Jobs Server Subserver Redirect
    > > Status/(Debug)
    > > webmasterptr@hoser2 enabled enabled 0 none none
    > >
    > > Ideas???? Printer is an HP Laserjet 5N, nothing fancy.
    > >
    > > Ringo

    >
    > ok 2 things to try, edit the /etc/cups/mime.types and uncomment the last
    > line that says
    >
    > application/octet-stream
    >
    > and then edit the mime.convs and also uncomment the last line showing
    >
    > application/octet-stream application/vnd.cups-raw 0 -
    >
    > then restart cups, then at the prompt type
    >
    > lpoptions -o raw
    >
    > then retry printing from your windows machine.
    >
    > If you are still getting premission errors, make sure your spool
    > directory is writable by the guest account so it can spool the print job.
    >
    > See how you go with that
    >
    > Spyro



    Hello,

    Actually I found the final piece that got it working (thanks to
    someone on IRC). I switched my driver to HP Laserjet 5 Postscript and
    it started working great. I'm not sure why I need to use a postscript
    driver instead of the regular one, but it works great now.

    Thanks for all the info and ideas --

    Ringo

+ Reply to Thread