Bug 5089 - Windows users cannot print through Samba
Windows users cannot print through Samba
Status: RESOLVED INVALID
Product: Samba 3.0
Classification: Unclassified
Component: Printing
3.0.27
x86 Linux
: P3 major
: none
Assigned To: Gerald (Jerry) Carter
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-17 08:59 UTC by Luis A. Florit
Modified: 2007-11-26 08:10 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luis A. Florit 2007-11-17 08:59:39 UTC
After upgrading from Fedora 6 to Fedora 8, Windows XP users cannot print 
anymore to a local printer in the Fedora 8 box. I'm using the same smb.conf 
file (below). Although I found no errors, the job just is not printed. 
Users of the Linux box print normally.

Versions: samba-3.0.27-0.fc8 and cups-1.3.4-3.fc8

To reproduce:
1. Window user installs printer
2. He sends job to the printer, and it appears to have been printed normally, 
but nothing at the printer.
3. At the linux box, when the window user sends the job, 'lpq' shows activity 
exactly as if normal printing was done:

# lpq
lp0 is ready
no entries
# lpq
lp0 is ready and printing
Rank    Owner   Job     File(s)                         Total Size
active  nobody  118     smbprn.00000018.IZZtzO          8192 bytes
# lpq
lp0 is ready
no entries


Additional info:

---> smb.conf file:
[global]
    workgroup = NINHO
    server string = Samba Server
    interfaces = eth1
    security = SHARE
    log file = /var/log/samba/log.%m
    max log size = 100
    name resolve order = bcast lmhosts host wins
    deadtime = 3
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    printcap name = /etc/printcap
    dns proxy = No
    idmap uid = 16777216-33554431
    idmap gid = 16777216-33554431
    hosts allow = 192.168.0.2, 192.168.0.3
    cups options = raw

[printers]
    comment = All Printers
    path = /var/spool/samba
    public = Yes
    guest ok = Yes
    printable = Yes
    browseable = No

---> cups access.log file shows no problems, and at the time of printing lots 
of lines like:

localhost - - [15/Nov/2007:21:01:04 -0200] "POST / HTTP/1.1" 200 416 
CUPS-Get-Printers successful-ok
localhost - - [15/Nov/2007:21:01:04 -0200] "POST / HTTP/1.1" 200 416 
CUPS-Get-Classes successful-ok
localhost - - [15/Nov/2007:21:01:04 -0200] "POST / HTTP/1.1" 200 75 
CUPS-Get-Default successful-ok
localhost - - [15/Nov/2007:21:01:04 -0200] "POST / HTTP/1.1" 200 119 
Get-Printer-Attributes successful-ok
localhost - - [15/Nov/2007:21:01:04 -0200] "POST / HTTP/1.1" 200 119 Get-Jobs 
successful-ok

---> cups error.log file shows nothing strange:

I [15/Nov/2007:21:01:07 -0200] [Job 118] Adding start banner page "none".
I [15/Nov/2007:21:01:07 -0200] [Job 118] Adding job file of type 
application/octet-stream.
I [15/Nov/2007:21:01:07 -0200] [Job 118] Adding end banner page "none".
I [15/Nov/2007:21:01:07 -0200] [Job 118] Queued on "lp0" by "nobody".
I [15/Nov/2007:21:01:07 -0200] [Job 118] Started 
backend /usr/lib/cups/backend/hp (PID 25507)
I [15/Nov/2007:21:01:09 -0200] [Job 118] Completed successfully.

---> page.log cups shows also nothing strange:

lp0 nobody 118 [15/Nov/2007:21:01:07 -0200] 1 1 - localhost
Comment 1 Gerald (Jerry) Carter 2007-11-26 08:10:11 UTC
If the jobs sgets to CUPS correctly, but CUPS doesn't print it, it is a 
CUPS issue.  Samba is not involved after the  job is handed off to the 
underlying printing system.