Arch Linux

Modeler

Member

From: United Kingdom

Registered: 2011-07-28

Posts: 70

IPP shared printer works with Windows clients but not with Linux!

Hi all,

I have an absurd problem with my Epson Stylus Photo R200 printer. It is configured using CUPS+Gutenprint v5.2.11 and prints fine from the machine to which it is locally attached. It is shared via IPP (URI http://192.168.0.4:631/printers/EPSON_S … hoto_R200) and works perfectly from my Windows 10 installation, however I cannot print to it from another Arch Linux box!

The job shows as completed in the CUPS web console, but the printer never reacts. /var/log/cups/access_log on both the client and server shows:

192.168.0.21 - - [16/Nov/2016:23:04:42 +0000] "POST /printers/EPSON_Stylus_Photo_R200 HTTP/1.1" 200 241 Validate-Job successful-ok
192.168.0.21 - - [16/Nov/2016:23:04:42 +0000] "POST /printers/EPSON_Stylus_Photo_R200 HTTP/1.1" 200 194 Create-Job successful-ok
192.168.0.21 - - [16/Nov/2016:23:04:42 +0000] "POST /printers/EPSON_Stylus_Photo_R200 HTTP/1.1" 200 7866046 Send-Document successful-ok

There are no errors in error_log, but nothing appears in page_log. It's as if the print just gets black-holed. Oddly I can print a test page from my Arch Linux client using the local CUPS front end, I just can't print documents (tried printing from gedit, LibreOffice, Chromium and such). As a sanity check I tried setting up a shared printer using cups-pdf over IPP, which seems to work fine so it's not looking like user permissions or anything like that.

I know it's an old printer and probably doesn't work too well with Linux in general, but my Arch Linux server is currently providing seamless print services to Windows clients and nothing to other Linux boxes. Any help would be really appreciated.

---

Wirth's law: "Software is getting slower more rapidly than hardware becomes faster"

pypi

Wiki Maintainer

Registered: 2014-04-22

Posts: 250

Re: IPP shared printer works with Windows clients but not with Linux!

It sounds like you have been fairly careful! Have you configured either the server or the client as a raw queue?

It might be helpful if you set the log level to debug, tried to print, and then posted the output - perhaps on both the server and the client?