Windows printing via cups

In this case the Windows client systems access the CUPS print queue as if it was a network printer i. Windows can usually send print data also via LPD protocol. See your Windows documentation how to set up printing this way for your particular Windows version. Up to CUPS 1. Since CUPS 2. Instead additional raw queues must be used, see below.

Nowadays Windows versions can usually send print data also via IPP. In this case the only reliable way to enforce raw printing on the CUPS server is to create an additional raw queue for each printer and use the raw queue when printing from Windows. When filtering should take place on the CUPS server, a pre-filtering process into PostScript must happen on Windows client systems see above. This is done with PostScript drivers for Windows.

The wikis are now using the new authentication system. Jump to: navigation , search. Notify me of new comments via email. Notify me of new posts via email. Skip to content. Share this: Twitter Facebook.

Like this: Like Loading This entry was posted in Uncategorized. Bookmark the permalink. March 6, at am. December 27, at am. Leave a Reply Cancel reply Enter your comment here One has to login using the domain account and the printed pages are payed using PAS credit. Note: newer versions of CUPS along with the system-config-printer graphical front-end seem to be able to print without customisation. So you can forget about the rest of the page.

It may be useful to note my experience with some Infotec multi-function copiers. Using the PCL queue takes more processing on the client but seems to avoid this problem. CUPS uses smbspool 8 to print pages to windows servers. This did not appear to work, whereas printing with smbclient 1 did some relief. Wanting to get it working, I created a custom CUPS backend that uses the latter instead of the former. This also allowed me to solve the problem of the windows password being visible in the device uri which is shown in the web interface.

Note that this still is a work in progress: it is being used with success, but now and then I encounter issues.