There seem to be several levels of confusion here. First, in this
situation, the D-Link print server is acting like a remote host which has
a printer attached to it. It's actually the D-Link you're talking to when
sending a print job to the printer. The D-Link then spools the job to the
printer.
So, as far as the
rm=
field is concerned, it doesn't matter what kind of printer you have or
what you feel like calling it. What matters is what the host name of the
D-Link print server is. A host name must map to an IP address - where is
the IP address for "deskjet" defined and does the print server know
anything about it?
Second, I'm not at all sure that you can use lpc to control a printer on a
remote machine. This would a pretty major security problem. Since the
D-Link's only job in life is to spool print jobs, it better have lpd
turned on automatically. If not, then there is some way to
telnet to the device in order to configure it to run lpd when turned on.
I'm pretty sure that the documentation that comes with the print server
explains a good bit of this; a little RTFM would have certainly helped the
questioner to formulate a better question.
---------- Forwarded message ----------
Date: Thu, 23 Mar 2000 22:47:02 -0600 (CST)
From: Jacob Brown <root@localhost>
To: [EMAIL PROTECTED]
Subject: Need help on Network Printer
I recently baught a D-Link print server for my printer so I can print from
any computer over my network (Solaris, Linux, Winblows, etc) and set it up
just like the manual said to by editing the /etc/printcap to something
like:
lp:\
:sd=/var/spool/lp:\
:mx#0:\
:sh:\
:rm=deskjet:\
:rp=lpt1:
which looks pretty good after reading the printing howto on linuxdoc, but
when I try to start lpc (lpc start lp) I get this:
lp:
lpc: connect: Connection refused
couldn't start daemon
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
