Re: Remote printing from a Solaris box to a remote Debian-CUPS server
thank you for your info. I have not had the time to immediately apply your
advice, but now I am eagerly trying again to set up my printing network.
According to your advice I read the man-pages and inserted the named line into
the "/etc/inetd.conf"-file. I restarted the "inetd"-daemon and the
"cupsd"-daemon as well, but printing from my SolarisBox to the remote
"Debian-system" is still impossible. When launching a print job from the
SolarisBox, an error message appears in its console window telling me:
Message from kap on SolarisBox (???) [ Tue Aug 16 13:31:28 ] ...
Error transfering print job 0
check queue for (rljet4p@Debian-system)
Meanwhile I learned from the docs that the inetd-daemon is listening on port 515
for incoming print jobs; in which case the cups-lpd daemon is started to handle
the job. What I don't know is: How can I tell whether the TCP-connection from
the SolarisBox to the Debian-system is OK? Is there a means to test this
connection? A sort of "ping" perhaps?
Any help is greatly appreciated.
Richard Mortimer wrote:
> man cups-lpd
> It suggests adding something like
> printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd
> -o document-format=application/octet-stream
> to /etc/inetd.conf
> Be sure to reload inetd after adding that /etc/init.d/inetd reload
> > -----Original Message-----
> > From: firstname.lastname@example.org [mailto:email@example.com] On Behalf
> > Of F. Kappen
> > Sent: 12 August 2005 13:28
> > To: firstname.lastname@example.org
> > Subject: Remote printing from a Solaris box to a remote
> > Debian-CUPS server
> > Hi all,
> > meanwhile my Ultra1 (sarge, kernel 2.4.27-2) can print via
> > its serial port to the attached HP-Laserjet4P; the spooler I
> > use is CUPS. Next thing I want to do is using this printer as
> > a remote printer. This is difficult in so far as the print
> > client is no Debian system, but a SUN box running Solaris 9.
> > On the print client (SUN Solaris9) I added the remote printer
> > with the command:
> > SolarisBox:# lpadmin -p rljet4p -s <remote debian system>
> > A ping from the SolarisBox to the remote "Debian-system" is OK:
> > SolarisBox:# ping <debian-system>
> > <debian-system> is alive
> > However checking the remote printer with
> > SolarisBox:# lpstat -p ljet4p
> > printer ljet4p faulted printing ljet4p-0. enabled since Aug
> > 12 13:10 2005. available.
> > server <debian-system> not responding
> > results in this error message. Although I edited the
> > "/etc/cups/cupsd.conf" file and inserted a line:
> > "Allow From <SolarisBox> "
> > I guess the SolarisBox uses the TCP-protocol, but I don't
> > know which port it uses. Also, I'm not sure if the CUPS
> > spooler on the remote Debian print-server can catch the
> > lpd-request from the SolarisBox at all and if so, which port
> > does the spooler use.? I browsed through the documentation
> > and googled the web, but I found no thread or doc that deals
> > with my problem. The only hint I found was a doc of the
> > suse-distribution, which mentions a LPD-protocol "cups-lpd".
> > http://www.novell.com/documentation/suse91/suselinux-adminguid
> However, I found nothing adequate in the Debian distribution.
> I am aware that my problem is not an all day issue, but maybe someone of
> this list has had the same idea and knows more about this subject. Please
> let me know.