On Wed, 2011-09-28 at 12:01 -0800, peasthope@shaw.ca wrote: [...] > > Now your printer is accessible using the IPP protocol ... > > lpr is needed here. > cups-bsd is installed and should provide a functional lpr. To be honest I never used lpr, although it is known to work with cups. Personally I use IPP and Samba, as most clients are either Windows or Linux, I'm satisfied with those. > > > ipp://hostname:631/printers/printername > > replace hostname with the hostname or IP of your linux server and > > replace 'printername' with the actual printername. > > The client requested printing of Test by lpr and made this report. > Desktops.PrintDoc HPLaserJet1100@172.24.1.1 MY:Test Ok > LPR: HPLaserJet1100@172.24.1.1 connecting failed, res = 1 > > This appeared in cupsserver:/var/log/cups/error_log. [...] > > This is the tcpdump from another request. [...] > > Any further thoughts? Check your /etc/cupsd.conf file, there should be a line somewhere near the top that reads "BrowseRemoteProtocols CUPS" or similar, this is a list of 'protocols' cups offers to its clients, perhaps you need to add the option lpd and/or lpr (documentation I briefly looked at doesn't mention lpr, only lpd). There is also a <Location /> ... </Location> directive, inside are an "Order" option and an "Allow" and/or "deny" option, make sure to allow your clients here, I have this set to "Allow all". Unwanted hosts are blocked on the firewall level in my case. Bear in mind that I'm not a cups expert by any means, nor have I tried to get cups working with lpr. > > Thanks, ... Peter E. > > -- > Telephone 1 360 450 2132. bcc: peasthope at shaw.ca > Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. > Personal pages http://members.shaw.ca/peasthope/ . > > Kind regards, Steven
Attachment:
signature.asc
Description: This is a digitally signed message part