MS Windows client cannot print to the CUPS printer server

[Ananda Putra]

Bellow is the error log from /var/log/cups/error_log
I [24/Apr/2006:16:50:16 +0700] Print-Job client-error-document-format-not-supported: Unsupported format 'application/octet-stream'!

The error occurred when Ms. Windows printing to the cups.

Bellow is my /etc/cups/cupsd.conf
===
LogLevel warning

# Administrator user group...
SystemGroup lpadmin

# Only listen for connections from the local machine.
# Listen localhost:631
# Listen /var/run/cups/cups.sock

# Show shared printers on the local network.
# Browsing On
BrowseOrder allow,deny
BrowseAllow @LOCAL

# Default authentication type, when authentication is required...
DefaultAuthType Basic

# Restrict access to the server...
<Location />
  Order allow,deny
  Allow localhost
  Allow 192.168.1.*
</Location>

# Restrict access to the admin pages...
<Location /admin>
  Order allow,deny
  Allow localhost
</Location>

# Restrict access to configuration files...
<Location /admin/conf>
  AuthType Basic
  Require user @SYSTEM
  Order allow,deny
  Allow localhost
</Location>

# Set the default printer/job policies...
<Policy default>
  # Job-related operations must be done by the owner or an adminstrator...
  <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  # All administration operations require an adminstrator to authenticate...
  <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default>
    AuthType Basic
    Require user @SYSTEM
    Order deny,allow
  </Limit>

  # Only the owner or an administrator can cancel or authenticate a job...
  <Limit Cancel-Job CUPS-Authenticate-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  <Limit All>
    Order deny,allow
  </Limit>
</Policy>

# Include files in /etc/cups/conf.d
Include /etc/cups/cups.d/ports.conf
Include /etc/cups/cups.d/browse.conf
===

/etc/cups/cups.d/ports.conf:
===
Listen /var/run/cups/cups.sock
Port 631
===

This line is in /etc/cups/mime.types:
application/octet-stream

and this line is in /etc/cups/mime.convs
application/octet-stream application/vnd.cups-raw 0 -

[Ananda Putra (ananda-putra)]

Additional info:
I'm using Epson LX-300+ dot matrix printer (I use LX-1050 as the driver) and HP Laserjet 1300 printer. The above problem is only happen when Windows client do printing to the LX-300+. There is no problem when printing to the Laserjet 1300.

[Michael Crider (mecrider)]

I am having the exact same trouble printing to a HP Deskjet 920C. I have no trouble printing to a LaserJet 1100. I edited mime.types and mime.convs and restarted /etc/init.d/cupsys, but it did not fix the problem. However, I also noticed that /etc/cups contains raw.types and raw.convs with these lines already uncommented, so I don't know if that was necessary.

[Michael Crider (mecrider)]

I created a raw print queue on Dapper and directed Windows to print to it using the deskjet 920c driver for windows. That works fine.

[Ryan T. Sammartino (ryan-sammartino)]

I am also having this issue with a HP DeskJet 895Cxi. Uncommenting the octet-stream mime types in /etc/cups/mime.convs did not help. Printing locally works no problem (as long as I remember to "modprobe lp"... why isn't that automatc?)

I am not at all sure how to create a "raw print queue" as Michael Crider suggests (nor do I think that is a proper "solution"... my printer was working just fine locally and via Samba when I decided to dump Mandriva a week ago).

If I print from another Ubuntu (Breezy) machine using any application's GUI (or trying to print a test page), I get the error.

But if I open a terminal and do (e.g.)

$lpr -l foo.pdf

then the PDF file will print.

So... something seems to have gone haywire with the filters.

[Michael Crider (mecrider)]

Ryan, I agree that I didn't have a solution, just a workaround until it is fixed, that also might give a clue on what is not working. The steps I did was:
System -> Administration -> Printing
New Printer
Local Printer, mark proper port
Manufacturer: Raw, Model: Queue, Apply
You can then print from Windows to the printer named Queue. Otherwise all of my experience is the same as yours (except lp does load automatically for me; I don't know what's going on with that).

[Martin Pitt (pitti)]

This is most likely a duplicate of bug 39484, which will be fixed soon. Leaving as Needsinfo until that is fixed.

[Ryan T. Sammartino (ryan-sammartino)]

Bug 39484 is now fixed but I'm just letting you know I won't be able to confirm the fix for 3 weeks as I am travelling.

If nobody else can confirm that that fix also fixes this then I'll do the testing immediately upon my return.

[Mario Limonciello (superm1)]

Isn't 3 weeks a little past the release date for Dapper? Hopefully someone
can confirm prior to that.

On 5/17/06, Ryan T. Sammartino <email address hidden> wrote:
>
> *** This bug is a duplicate of bug 39484 ***
>
> Bug 39484 is now fixed but I'm just letting you know I won't be able to
> confirm the fix for 3 weeks as I am travelling.
>
> If nobody else can confirm that that fix also fixes this then I'll do
> the testing immediately upon my return.
>
> --
> MS Windows client cannot print to the CUPS printer server
> https://launchpad.net/bugs/41077
>

--
Mario Limonciello
<email address hidden>

[Michael Crider (mecrider)]

I will confirm that I can now print from Windows 2000 to my DeskJet 920C with both SMB and IPP protocols. Neither worked before, and I changed nothing besides applying all updates.

[Mark Stosberg (markstos)]

Changing this to a status of "fixed", as someone said it "works for me", and there have been no other follow-up comments in over a year.