
Now, if you have a CUPS server that is not on your local subnet, there is a simpler way to print to the printers it serves than described by the hint. When the CUPS server is on a remote subnet, it is hard to get printing to the printers it serves to work from a Mac. Connections to CUPS servers on your local subnet do occur automatically. Comments below that say "it just worked without any intervention from me" are clearly connecting to CUPS servers on their local subnet. If you find some way to select Raw from Apple's Printer Setup Utility, please post it in the comments.Ĭontrary to several comments below, there is a problem printing to printers served by CUPS servers that are not on your local subnet. This means you have to select it every time. Because we have to set up the printer in this manner, it will appear in our print settings as a 'Shared' printer and thus cannot be the default printer (if you know of a way to get it back into the list of local printers, please post in the comments). So what's the problem? We need to use the web interface to set this printer up because Apple (in their wisdom) have decided not to include Raw printing in their setup.
#Mac os 10.9.5 printing to cups mac
Make the printer on the mac into a 'raw' printer.

The work-around is to make one end of the chain a 'raw' printer. The remote CUPS server will then try to render the already rendered file and will give a no_file error.

It will then send the rendered file to the remote CUPS server. This is because Panther runs CUPS as its own print engine, and will attempt to render the PostScript for you once you select your correct printer driver. In Panther, it can be difficult to print to a remote CUPS server.
