I have been having a printing problem recently on a setup that has worked
for quite some time. Configs below. The symtoms are slightly different
on a W2K and a WinME workstation, but the result is the same; no printed
output. However, when I print from the local Unix server or from any
other Unix server in the network the output is as expected.
The W2K machine reports 'Access denied, unable to connect' when the
printer is selected via the Printers window.
When I add in the 'use client driver = yes' directive the symptoms are
masked in that the printer shows as 'Ready' in the Printers window but,
still, no printed output and the printing process hangs.
I've tried all kinds of things to fix this, I've looked thru mail
archives
and I've run smbd interactively with debugging turned on to no avail. I
have seen this same question asked by others in the archives but no
resolution.
Any further pointers for troubleshooting would be much appreciated.
-Steve
----
smb.conf:
[global]
log file = /var/log/samba/log.%m
printing = BSD
printcap name = /etc/printcap
print command = /usr/bin/lpr -P%p -r %s
[printer]
# use client driver = yes
path = /var/spool/lpd/spit
printable = yes
printer name = lp
read only = yes
guest ok = yes
printcap:
dj932c|color|HP DeskJet 932c:\
:sh:mx#0:\
:lp=/dev/lpt0:sd=/var/spool/lpd/spit:\
:if=/usr/local/libexec/magicfilter/dj550c-filter:\
:lf=/var/log/lpd-errors:
Further to this, I ran the following putting smbd into interactive mode anc capturing the output: # script -t 1 logger /usr/local/sbin/smbd -i -d 4 -l /tmp There is a whole section in the debug output that ends with an access denied message. There are two messages; "access check was FAILURE" and "access DENIED for printer open". I haven't a clue what the debug leading up to that means. Any pointers? -Steve --- <debug extract> vfs_ChDir to /tmp trans <\PIPE\> data=2316 params=0 setup=2 named pipe command on <> name search for pipe pnum=744b Got API command 0x26 on pipe "spoolss" (pnum 744b)free_pipe_context: destroying talloc pool of size 0 Doing \PIPE\spoolss api_rpcTNP: api_spoolss_rpc op 0x45 - api_rpcTNP: pipe 29771 rpc command: SPOOLS S_OPENPRINTEREX checking name: \\good\printer Opened policy hnd[2] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D ... ..... .......[010] B8 81 00 00 .... Setting printer type=\\good\printer Printer is a printer Setting printer name=\\good\printer (len=14) set_printer_hnd_name: Printer found: printer -> printer Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... short name:printer se_access_check: user sid is S-1-5-21-1188926781-616364094-2007133261-3002 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-1001 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-1107 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-2801 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-21001 se_access_check: also S-1-1-0 se_access_check: also S-1-5-2 se_access_check: also S-1-5-11 access check was FAILURE access DENIED for printer open Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... Closed policy </debug extract> * Steve Carter <scarter@pobox.com> [021106 16:53]:> I have been having a printing problem recently on a setup that has worked > for quite some time. Configs below. The symtoms are slightly different > on a W2K and a WinME workstation, but the result is the same; no printed > output. However, when I print from the local Unix server or from any > other Unix server in the network the output is as expected. > > The W2K machine reports 'Access denied, unable to connect' when the > printer is selected via the Printers window. > > When I add in the 'use client driver = yes' directive the symptoms are > masked in that the printer shows as 'Ready' in the Printers window but, > still, no printed output and the printing process hangs. > > I've tried all kinds of things to fix this, I've looked thru mail archives > and I've run smbd interactively with debugging turned on to no avail. I > have seen this same question asked by others in the archives but no > resolution. > > Any further pointers for troubleshooting would be much appreciated. > > -Steve > > ---- > > smb.conf: > > [global] > log file = /var/log/samba/log.%m > > printing = BSD > printcap name = /etc/printcap > print command = /usr/bin/lpr -P%p -r %s > [printer] > # use client driver = yes > path = /var/spool/lpd/spit > printable = yes > printer name = lp > read only = yes > guest ok = yes > > printcap: > > dj932c|color|HP DeskJet 932c:\ > :sh:mx#0:\ > :lp=/dev/lpt0:sd=/var/spool/lpd/spit:\ > :if=/usr/local/libexec/magicfilter/dj550c-filter:\ > :lf=/var/log/lpd-errors:
I'm no expert with printer problems but have you tried setting the perms on your /var/spool/lpd/spit directory to 777? Just a thought, Noel -----Original Message----- From: Steve Carter [mailto:scarter@pobox.com] Sent: 07 November 2002 00:54 To: samba@lists.samba.org Subject: Re: [Samba] Printing: Access denied, unable to connect Further to this, I ran the following putting smbd into interactive mode anc capturing the output: # script -t 1 logger /usr/local/sbin/smbd -i -d 4 -l /tmp There is a whole section in the debug output that ends with an access denied message. There are two messages; "access check was FAILURE" and "access DENIED for printer open". I haven't a clue what the debug leading up to that means. Any pointers? -Steve --- <debug extract> vfs_ChDir to /tmp trans <\PIPE\> data=2316 params=0 setup=2 named pipe command on <> name search for pipe pnum=744b Got API command 0x26 on pipe "spoolss" (pnum 744b)free_pipe_context: destroying talloc pool of size 0 Doing \PIPE\spoolss api_rpcTNP: api_spoolss_rpc op 0x45 - api_rpcTNP: pipe 29771 rpc command: SPOOLS S_OPENPRINTEREX checking name: \\good\printer Opened policy hnd[2] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D ... ..... .......[010] B8 81 00 00 .... Setting printer type=\\good\printer Printer is a printer Setting printer name=\\good\printer (len=14) set_printer_hnd_name: Printer found: printer -> printer Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... short name:printer se_access_check: user sid is S-1-5-21-1188926781-616364094-2007133261-3002 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-1001 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-1107 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-2801 se_access_check: also S-1-5-21-1188926781-616364094-2007133261-21001 se_access_check: also S-1-1-0 se_access_check: also S-1-5-2 se_access_check: also S-1-5-11 access check was FAILURE access DENIED for printer open Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... Found policy hnd[0] [000] 00 00 00 00 02 00 00 00 00 00 00 00 00 B6 C9 3D .... .... .......[010] B8 81 00 00 .... Closed policy </debug extract> * Steve Carter <scarter@pobox.com> [021106 16:53]:> I have been having a printing problem recently on a setup that has worked > for quite some time. Configs below. The symtoms are slightly different > on a W2K and a WinME workstation, but the result is the same; no printed > output. However, when I print from the local Unix server or from any > other Unix server in the network the output is as expected. > > The W2K machine reports 'Access denied, unable to connect' when the > printer is selected via the Printers window. > > When I add in the 'use client driver = yes' directive the symptoms are > masked in that the printer shows as 'Ready' in the Printers window but, > still, no printed output and the printing process hangs. > > I've tried all kinds of things to fix this, I've looked thru mail archives > and I've run smbd interactively with debugging turned on to no avail. I > have seen this same question asked by others in the archives but no > resolution. > > Any further pointers for troubleshooting would be much appreciated. > > -Steve > > ---- > > smb.conf: > > [global] > log file = /var/log/samba/log.%m > > printing = BSD > printcap name = /etc/printcap > print command = /usr/bin/lpr -P%p -r %s > [printer] > # use client driver = yes > path = /var/spool/lpd/spit > printable = yes > printer name = lp > read only = yes > guest ok = yes > > printcap: > > dj932c|color|HP DeskJet 932c:\ > :sh:mx#0:\ > :lp=/dev/lpt0:sd=/var/spool/lpd/spit:\ > :if=/usr/local/libexec/magicfilter/dj550c-filter:\ > :lf=/var/log/lpd-errors:-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.410 / Virus Database: 231 - Release Date: 31/10/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.410 / Virus Database: 231 - Release Date: 31/10/2002
Steve,
Do you have the samba guest connection set up?
I think you need it if you have guest ok=yes.
e.g.
Map to Guest = Bad User
Guest Account = ftp (or another no-login account)
(I created and use smb_nobody)
The Access Denied may be for the IPC$ connection,
and IIRC the guest/bad user account may
satisfy this.
Boost the debug level in [Global] to 3 or
higher to see the messages re: the access
denied - you may find more info there than you
would via tcpdump.
Jim
> -----Original Message-----
> From: Steve Carter [mailto:scarter@pobox.com]
> Sent: Sunday, November 17, 2002 11:24 AM
> To: samba@lists.samba.org
> Subject: Re: [Samba] Printing: Access denied, unable to connect
>
>
> I doubt it'll help much, but I've done some more investigation.
The
> original system was a FreeBSD 4.7 server running samba 2.2.6:
>
> # smbd -V
> Version 2.2.6
> # uname -a
> FreeBSD xxxx.xxxx.xxx 4.7-STABLE FreeBSD 4.7-STABLE #0: Wed Oct 16
> 17:38:23 MST 2002 root@xxxx.xxxx.xxx:/usr/src/sys/compile/XXXX i386
>
> I built a new box running Debian Linux 2.2r7 with samba 2.2.3 and CUPS
> v1.1.14:
>
> # uname -a
> Linux xxxx.xxxx.xxx 2.2.19 #1 Sat Jun 9 13:04:06 EST 2001 i586 unknown
> # smbd -V
> Version 2.2.3a-6 for Debian
>
> I also shutdown every other SMB box on my network and worked with one
> Windows 2000 laptop and the aforementioned Debian machine. I
> bet you can
> guess now that I got the very same error message on the W2K
> laptop whether
> using the Debian/cups or the FreeBSD/lpd servers; "Access
> Denied, unable
> to connect".
>
> This is totally silly, and there appears to be nothing in the logs (of
> anything) to indicate exactly what is denying access. All I
> can think of
> is to use tcpdump and hope I can grab something interesting
> but SMB is so
> chatty it'll be almost impossible.
>
> Anyone else seeing these same errors?
>
> -Steve
>
> * Steve Carter <scarter@pobox.com> [021106 17:53]:
> > > smb.conf:
> > >
> > > [global]
> > > log file = /var/log/samba/log.%m
> > >
> > > printing = BSD
> > > printcap name = /etc/printcap
> > > print command = /usr/bin/lpr -P%p -r %s
> > > [printer]
> > > # use client driver = yes
> > > path = /var/spool/lpd/spit
> > > printable = yes
> > > printer name = lp
> > > read only = yes
> > > guest ok = yes
> > >
> > > printcap:
> > >
> > > dj932c|color|HP DeskJet 932c:\
> > > :sh:mx#0:\
> > > :lp=/dev/lpt0:sd=/var/spool/lpd/spit:\
> > > :if=/usr/local/libexec/magicfilter/dj550c-filter:\
> > > :lf=/var/log/lpd-errors:
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>