Re(2): CUPS network printing
# From: Steven redalert.comman...@gmail.com # Date: Thu, 22 Sep 2011 23:34:22 +0200 On the cups webinterface click administration, and make sure to check the box Share printers connected to this system, save these settings. Then go to printers, select your printer and use the dropdownbox to select edit printer, click continue, then in the next screen check Share this printer and click continue. So far, so good. Now your printer is accessible using the IPP protocol ... lpr is needed here. cups-bsd is installed and should provide a functional lpr. 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. D [22/Sep/2011:15:40:09 -0700] cupsdAcceptClient: 12 from localhost:631 (IPv4) D [22/Sep/2011:15:40:09 -0700] cupsdReadClient: 12 GET /admin/log/error_log HTTP/1.1 D [22/Sep/2011:15:40:09 -0700] cupsdSetBusyState: Active clients D [22/Sep/2011:15:40:09 -0700] cupsdAuthorize: Authorized as root using Basic This is the tcpdump from another request. root@cupsserver:/# tcpdump -i LocBel7411cc tcp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on LocBel7411cc, link-type EN10MB (Ethernet), capture size 65535 bytes 16:00:46.740617 IP cantor.invalid.721 172.24.1.1.printer: Flags [S], seq 129592, win 8192, options [mss 1420], length 0 16:00:46.740711 IP 172.24.1.1.printer cantor.invalid.721: Flags [R.], seq 0, ack 129593, win 0, length 0 ... 16:00:46.762612 IP cantor.invalid.731 172.24.1.1.printer: Flags [S], seq 138632, win 8192, options [mss 1420], length 0 16:00:46.762631 IP 172.24.1.1.printer cantor.invalid.731: Flags [R.], seq 0, ack 138633, win 0, length 0 ^C 22 packets captured 22 packets received by filter 0 packets dropped by kernel root@cupsserver:/# ^C Any further thoughts? 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/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171057148.49269.46023@cantor.invalid
Re(2): CUPS network printing
# From: Steven redalert.comman...@gmail.com # Date: Thu, 22 Sep 2011 23:34:22 +0200 On the cups webinterface click administration, and make sure to check the box Share printers connected to this system, save these settings. Then go to printers, select your printer and use the dropdownbox to select edit printer, click continue, then in the next screen check Share this printer and click continue. So far, so good. Now your printer is accessible using the IPP protocol ... lpr is needed here. cups-bsd is installed and should provide a functional lpr. 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. D [22/Sep/2011:15:40:09 -0700] cupsdAcceptClient: 12 from localhost:631 (IPv4) D [22/Sep/2011:15:40:09 -0700] cupsdReadClient: 12 GET /admin/log/error_log HTTP/1.1 D [22/Sep/2011:15:40:09 -0700] cupsdSetBusyState: Active clients D [22/Sep/2011:15:40:09 -0700] cupsdAuthorize: Authorized as root using Basic This is the tcpdump from another request. root@cupsserver:/# tcpdump -i LocBel7411cc tcp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on LocBel7411cc, link-type EN10MB (Ethernet), capture size 65535 bytes 16:00:46.740617 IP cantor.invalid.721 172.24.1.1.printer: Flags [S], seq 129592, win 8192, options [mss 1420], length 0 16:00:46.740711 IP 172.24.1.1.printer cantor.invalid.721: Flags [R.], seq 0, ack 129593, win 0, length 0 ... 16:00:46.762612 IP cantor.invalid.731 172.24.1.1.printer: Flags [S], seq 138632, win 8192, options [mss 1420], length 0 16:00:46.762631 IP 172.24.1.1.printer cantor.invalid.731: Flags [R.], seq 0, ack 138633, win 0, length 0 ^C 22 packets captured 22 packets received by filter 0 packets dropped by kernel root@cupsserver:/# ^C Any further thoughts? 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/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171057148.53359.46026@cantor.invalid
Re: Re(2): CUPS network printing
On Wed, 2011-09-28 at 12:01 -0800, peasth...@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 signature.asc Description: This is a digitally signed message part
Re (3): CUPS network printing
From: Steven redalert.comman...@gmail.com Date: Wed, 28 Sep 2011 22:24:43 +0200 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 BrowseLocalProtocols. How do you interpret Local and Remote here? Local is the machine where cups runs while Remote is everything else? In any case I made this. BrowseRemoteProtocols CUPS dnssd lpd lpr BrowseLocalProtocols CUPS dnssd lpd lpr Also DefaultAuthType None for now. Also added Listen 172.24.1.1:515. Now the client reports this. Desktops.PrintDoc HPLaserJet1100@172.24.1.1 file:Blah.html Ok LPR: HPLaserJet1100@172.24.1.1 sending 255 receive print job failed Appears that the Listen directive allowed the connection. That's progress. Now this appears in cupsserver:/var/log/cups/error_log. D [28/Sep/2011:15:16:35 -0700] cupsdAcceptClient: 13 from 172.24.1.2:515 (IPv4) E [28/Sep/2011:15:16:35 -0700] Unable to encrypt connection from 172.24.1.2 - A record packet with illegal version was received. D [28/Sep/2011:15:16:35 -0700] cupsdCloseClient: 13 Encrypt connection? Bug #635096? What is the 13 here? Enough for now. Thanks for the feedback, ... 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/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171057148.63177.46027@cantor.invalid
Re: CUPS network printing
On Thu, 22 Sep 2011 17:10:36 -0500 Joseph Lenox lenox.jos...@gmail.com wrote: On 09/22/2011 04:37 PM, Joe wrote: No, the printer only has an IP address if it's a standalone network printer. Such things do exist, but yours isn't one, or at least is not connected as one. Cups will be listening (by default) on port 631, on the computer's IP address. I can't remember if it listens to anything other than localhost by default, you may need to change the cupsd configuration file to allow connections from other machines. Check with netstat. If you have Windows machines in your network, then Samba is probably the best way to share the printer. Since I do that, I can't comment on the direct use of Cups over the network. My workstation has cupsd listening on all interfaces UDP, but only localhost TCP. I would assume that is the default, since there's never been a printer attached to this machine. With Windows Vista/7, it's pretty straightforward to add the CUPS URL for the printer directly as a networked printer. It should also work under XP, but it's been a while since I've had to deal with XP and networked printers. Samba would basically make the printer show up on browse. It's as simple as setting up a network printer under Vista/7 and entering http://address of sharing machine:631/printers/print_queue_name as the printer destination. You are implying it works, OK, I haven't tried it. But Windows has always had a 'Unix Printing' facility, it was just a bit flaky in times gone by. Despite many peoples' beliefs, Windows is no longer a terrible OS, but I prefer to use Microsoft when it stays in its comfort zone i.e. not attempting to connect with other peoples' systems, hence my preference for Samba. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110923084339.33f51...@jretrading.com
CUPS network printing
Folk, A printer is connected to a Squeeze system here with a parallel cable. CUPS is installed and there is no problem printing directly from the host. I'm interested to have this printer work for other machines on the LAN. http://www.cups.org/documentation.php/doc-1.5/network.html contains, Verifying the Printer Connection ... ping myprinter PING myprinter (192.0.2.2): 56 data bytes 64 bytes from 192.0.2.2: icmp_seq=0 ttl=15 time=5 ms. Whereas here, this is the result. root@dalton:/# ping HPLaserJet1100 ping: unknown host HPLaserJet1100 Seems that for network access, the printer must be assigned an IP address. Can anyone find documentation? Can the address be assigned in /etc/network/interfaces ? Otherwise, where? Thanks, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/fb719b7f6320f.4e7b3...@shaw.ca
Re: CUPS network printing
On Thu, 2011-09-22 at 13:25 -0700, PETER EASTHOPE wrote: Folk, A printer is connected to a Squeeze system here with a parallel cable. CUPS is installed and there is no problem printing directly from the host. I'm interested to have this printer work for other machines on the LAN. http://www.cups.org/documentation.php/doc-1.5/network.html contains, Verifying the Printer Connection ... ping myprinter PING myprinter (192.0.2.2): 56 data bytes 64 bytes from 192.0.2.2: icmp_seq=0 ttl=15 time=5 ms. Whereas here, this is the result. root@dalton:/# ping HPLaserJet1100 ping: unknown host HPLaserJet1100 Seems that for network access, the printer must be assigned an IP address. Can anyone find documentation? Can the address be assigned in /etc/network/interfaces ? Otherwise, where? No, the printer does not need an IP address, as the request will be forwarded/handled by your Linux machine and CUPS. If you have a browser on that machine got to http://localhost:631 otherwise use a browser on a different machine to connect, however in that case the /etc/cups/cupsd.conf file need to be edited (or simply use an ssh tunnel). On the cups webinterface click administration, and make sure to check the box Share printers connected to this system, save these settings. Then go to printers, select your printer and use the dropdownbox to select edit printer, click continue, then in the next screen check Share this printer and click continue. Now your printer is accessible using the IPP protocol with the url ipp://hostname:631/printers/printername replace hostname with the hostname or IP of your linux server and replace 'printername' with the actual printername. Of course you can do this without the web interface, I just find it easier this way. That should do the trick. You can also use Samba to share your printers, a printer configured this way in CUPS will automatically show up in the windows network the option load printers is set to yes in your /etc/samba/smb.conf file. Also set the options printing and printcap name to cups (without the quotes) Both methods can be used when printing from either MS Windows or Linux. Good luck Thanks, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: CUPS network printing
On Thu, 22 Sep 2011 13:25:39 -0700 PETER EASTHOPE peasth...@shaw.ca wrote: Folk, A printer is connected to a Squeeze system here with a parallel cable. CUPS is installed and there is no problem printing directly from the host. You are explicitly stating here that it is not a networked printer, it is a printer attached to a networked computer. Not the same thing. I'm interested to have this printer work for other machines on the LAN. http://www.cups.org/documentation.php/doc-1.5/network.html contains, Verifying the Printer Connection ... ping myprinter PING myprinter (192.0.2.2): 56 data bytes 64 bytes from 192.0.2.2: icmp_seq=0 ttl=15 time=5 ms. Whereas here, this is the result. root@dalton:/# ping HPLaserJet1100 ping: unknown host HPLaserJet1100 Seems that for network access, the printer must be assigned an IP address. Can anyone find documentation? Can the address be assigned in /etc/network/interfaces ? Otherwise, where? No, the printer only has an IP address if it's a standalone network printer. Such things do exist, but yours isn't one, or at least is not connected as one. Cups will be listening (by default) on port 631, on the computer's IP address. I can't remember if it listens to anything other than localhost by default, you may need to change the cupsd configuration file to allow connections from other machines. Check with netstat. If you have Windows machines in your network, then Samba is probably the best way to share the printer. Since I do that, I can't comment on the direct use of Cups over the network. My workstation has cupsd listening on all interfaces UDP, but only localhost TCP. I would assume that is the default, since there's never been a printer attached to this machine. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2011093732.69491...@jretrading.com
Re: CUPS network printing
On 09/22/2011 04:37 PM, Joe wrote: No, the printer only has an IP address if it's a standalone network printer. Such things do exist, but yours isn't one, or at least is not connected as one. Cups will be listening (by default) on port 631, on the computer's IP address. I can't remember if it listens to anything other than localhost by default, you may need to change the cupsd configuration file to allow connections from other machines. Check with netstat. If you have Windows machines in your network, then Samba is probably the best way to share the printer. Since I do that, I can't comment on the direct use of Cups over the network. My workstation has cupsd listening on all interfaces UDP, but only localhost TCP. I would assume that is the default, since there's never been a printer attached to this machine. With Windows Vista/7, it's pretty straightforward to add the CUPS URL for the printer directly as a networked printer. It should also work under XP, but it's been a while since I've had to deal with XP and networked printers. Samba would basically make the printer show up on browse. It's as simple as setting up a network printer under Vista/7 and entering http://address of sharing machine:631/printers/print_queue_name as the printer destination. --Joseph Lenox -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e7bb25c.3050...@gmail.com
