The Samba-Bugzilla – Bug 2010
Intel Print station - access denied when printing
Last modified: 2005-05-09 05:45:22 UTC
Unable to open print jobs in an intel print station (ethernet + 2 LPT ports)
Sidenote: intel print stations have names like PS0EBB39 - I have seen a few
references to the same problem around the net.
This seems to be due to a difference in the command used to open/close print
jobs. I did do a patch to samba 2.x that fixed this some time back, but I did
not successfully translate it to samba 3.0.0 (not sure why - I ended up with the
print job being sent but the print station did nothing). I might take another
crack at it against 3.0.8 soon.
SMBwrite <- even windows uses this rather than SMBsplwr
can you attach a raw network trace (tcpdump -w /tmp/bug2010.pcap -s 0 -i eth0)
with this bug report? Thanks.
I'm assuming you are printing using smbclient to connect
to the remote Intel print server.
Created attachment 832 [details]
partial fix to printstation access denied
Created attachment 833 [details]
network trace of bug under stock standard samba 3.0.8
Created attachment 834 [details]
network trace of bug under patched 3.0.8
The file is sent, but no output from printer yet.
(In reply to comment #1)
> can you attach a raw network trace (tcpdump -w /tmp/bug2010.pcap -s 0 -i eth0)
> with this bug report?
yes- I have also attached my partial patch against 3.0.8 - the file seems to be
written, but does not produce output on the printer - I expect this is due to
some form of corruption during the send (a little hard to detect as the printer
is a brother multifunction centre using a binary protocol).
The print job is generated correctly as uploading the file to the print
station's ftp server produces correct output (but a bug in the print server
leaves an EOF on the file leaving the printer in limbo after printing)
Small text files of a few lines are printed correctly (if sent to the printer as
> I'm assuming you are printing using smbclient to connect
> to the remote Intel print server.
yes - well CUPS smb support (calls smbspool), and manually calling smbclient.
Hmmm...this breaks printing against a Windows 200 SP4 print server....
$ cat /etc/hosts | bin/smbclient //windc/apple -UAdministrator \
-W BOOKS -c 'print -'
Domain=[BOOKS] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
ERRSRV - ERRerror (Non-specific error code.) opening remote spool stdin-31420
Needs more invesitgation
I get the same error when sending the job via
smbspool (as i would expect).
SMB (Server Message Block Protocol)
Server Component: SMB
Response to: 13
Time from request: 0.006411000 seconds
SMB Command: Open Print File (0xc0)
Error Class: Server Error (0x02)
Error Code: Non specific error code (0x0001)
I've applied to the patches to cliprint.c. Haven't found out
why the SMB_OPEN_PRINT_JOB fails against 2k servers yets.
closing this one. I've applied the SMBspl patch but not
changed smbclient to use these commands since they fail
against Win2k. And I don't have one of these Intel
print servers to poke at.