On Wed 16 Mar 2016 at 16:14:47 +0000, Brian wrote: > On Wed 16 Mar 2016 at 12:06:40 -0400, Gene Heskett wrote: > > > On Wednesday 16 March 2016 10:12:59 Brian wrote: > > > > > Now find a *small* PDF file and send it directly to the printer with > > > netcat: > > > > > > nc 192.168.71.20 9100 < file.pdf > > > > > > or > > > > > > nc BRN001BA9E3811F.local < file.pdf > > > > > > Does it print? > > > > Doesn't look like it: > > > > gene@coyote:~/Downloads$ nc BRN001BA9E3811F.local <7i77_layout.pdf > > no port[s] to connect to > > gene@coyote:~/Downloads$ nc 192.168.71.20 < 7i77_layout.pdf > > no port[s] to connect to > > Haven't you omitted the port to connect to? Just like I did for one of > the lines above. :(. Apologies. > > nc 192.168.71.20 9100 < 7i77_layout.pdf > ^^^^
It is a pity this correction to a simple command was not made and the outcome described. The txt record for the printer has pdl=application/octet-stream,image/urf" PDFs will not print. I own up to spreading misinformation if I implied they would. I now have the use of an HP AirPrint enabled printer (a 4200 series printer). The MIME types which are supported by this printer are pdl=application/vnd.hp-PCL,image/jpeg,application/PCLm,image/urf The only thing the printers have in common is image/urf. I have changed my mind about the AirPrint capabilty on his printer being a route to avoid using a proprietary driver. If Jarle Aase is printing now it is through the agency of the Brother .deb packages.