Re: remote printer configuration - cups
Derrick 'dman' Hudson wrote:
On Sun, Mar 30, 2003 at 07:02:49AM -0500, Tom Allison wrote:
| I have a printer which runs on a network connection.
|
| I scanned for ports and found ports associated with lpd (515), cups (631),
| and jetdirect (9100?) and was trying to configure a cups client.
Sounds like an HP JetDirect card connects the printer to the network.
| I installed the following packages:
| a2ps
| cupsys-bsd
| cupsys-client
| foomatic-bin
| foomatic-db
I would first install the 'cupsys' package. Then add a local queue
for the printer (use either the lpadmin command or the web interface
which you'll find at http://localhost:631/). Specify the correct
model so that data conversions work correctly. As for the device URI
you have a couple of choices :
lpd://<hostname>/<printername>
ipp://<hostname>:631/ipp/port1
socket://<hostname>:9100/
Naturally, <hostname> can be either a name or IP address. Names are
generally better.
The URIs can vary somewhat depending on the software and configuration
of the remote end. For example, with a cups server the ipp uri is
ipp://<hostname>/printers/<printername>. HP JetDirect cards use
"port1" for the first printer and "port2" for the second (some cards
have connections for 2 printers). The general concept is the same,
though.
You could probably get away without setting up a server if you use the
IPP URI, but you would have less control and flexibility. One of
CUPS' strong points is the ability to accept many types of input
(text, PS, PDF, JPG, PNG, etc.) and automatically convert it to
something the printer understands. That is all done server-side, so
without a "server" you lose that functionality.
| So I tried configuring it a direct configuration:
| foomatic-configure -s cups -n remoteraw -c socket://192.168.0.100:631/
This is really wrong -- the "socket" protocol (aka JetDirect) normally
uses port 9100. Port 631 is (normally) for the IPP protocol. Don't
try mixing and matching them unless you know for certain that the
server-side setup is unusual.
HTH,
-D
I started to try this approach and died here:
Setting up cupsys (1.1.15-4) ...
Starting CUPSys: cupsd.
tallison@penguin:~$ sudo foomatic-configure -s cups -n FS1900 -c
socket://192.168.0.100:9100 -p Kyocera-FS-1900 -d Postscript
Password:
Cannot read printers.conf file!
=======
I've installed the following (dpkg -l cup*)
dpkg -l cup*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
pn cup <none> (no description available)
un cups <none> (no description available)
pn cupsomatic-ppd <none> (no description available)
ii cupsys 1.1.15-4 Common UNIX Printing System(tm) - server
ii cupsys-bsd 1.1.15-4 Common UNIX Printing System(tm) - BSD
comman
ii cupsys-client 1.1.15-4 Common UNIX Printing System(tm) -
client pro
pn cupsys-driver- <none> (no description available)
pn cupsys-pstoras <none> (no description available)
in cupsys-pt <none> (no description available)
------------------------------------------------------------------------
Where does the printer.conf file come into play?
--
Cops never say good-bye. They're always hoping to see you again in the
line-up.
-- Raymond Chandler
Reply to: