HL-L2300D Problem

[CTSchorsch]

Hi,
i have a Problem with the HL-L2300D Printer:

-cups 2.2.1 on debian 9
-printing from linux is working fine, local and network
-printing von windows is not working:
D [10/Sep/2019:21:23:23 +0200] [Job 50] gstopdf argv[6] = 50 labor Testseite 1 job-uuid=urn:uuid:4388551e-66e5-3112-6f63-0a50bf2de54c usb-no-reattach usb-unidir job-originating-host-name=10.20.25.8 date-t
ime-at-creation= date-time-at-processing= time-at-creation=1568143403 time-at-processing=1568143403 /var/spool/cups/d00050-001
D [10/Sep/2019:21:23:23 +0200] [Job 50] PPD: /etc/cups/ppd/HLL2300D.ppd
D [10/Sep/2019:21:23:23 +0200] [Job 50] Loading USB quirks from "/usr/share/cups/usb".
D [10/Sep/2019:21:23:23 +0200] [Job 50] Loaded 132 quirks.
D [10/Sep/2019:21:23:23 +0200] [Job 50] Printing on printer with URI: usb://Brother/HL-L2300D%20series?serial=E73860M5N460828
D [10/Sep/2019:21:23:23 +0200] [Job 50] pdftopdf: Last filter determined by the PPD: brother_lpdwrapper_HLL2300D; FINAL_CONTENT_TYPE: application/vnd.cups-pdf => pdftopdf will not log pages in page_log.
D [10/Sep/2019:21:23:23 +0200] [Job 50] OUTFORMAT="PDF", so output format will be PDF
D [10/Sep/2019:21:23:23 +0200] [Job 50] libusb_get_device_list=4
D [10/Sep/2019:21:23:23 +0200] [Job 50] STATE: +connecting-to-device
D [10/Sep/2019:21:23:23 +0200] [Job 50] STATE: -connecting-to-device
E [10/Sep/2019:21:23:23 +0200] [Job 50] Can't detect file type
D [10/Sep/2019:21:23:23 +0200] [Job 50] PID 32089 (/usr/lib/cups/filter/gstopdf) stopped with status 1.
E [10/Sep/2019:21:23:23 +0200] [Job 50] loadFile failed: temp file: not a PDF file

Is there any solution ?
Regards
Georg

[pdewacht]

It looks like you're using the official Brother drivers. I can't help you with those. This project is about my non-official open source driver for these printers.

Though here the problem is not with the printer driver but with the configuration of your CUPS configuration and/or the Windows system. Your server is getting a print job it can't interpret.

CUPS and Windows handle printer drivers very differently: CUPS runs the printer driver on the server, Windows (as far as I know) always runs the printer driver on the client. I think what happened here is that you've installed a Brother printer driver on both client and server. That won't work.

If my guess is correct, you have two options to solve the problem:

• Create a raw CUPS queue for the Windows client.
• Use a generic Postscript/PDF driver on the Windows client. (The Debian wiki suggests using the "MS Publisher Color Printer" driver.)