lexmark hpjetdirect lpd

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

From: "Brian K. White" <brian@aljex.com>
References: <aRYF7.10860$Y6.658050@news1.rdc1.ct.home.com> 
Subject: Re: jetdirect 500x
Date: Wed, 07 Nov 2001 09:47:41 GMT


"Nick Bessey" <nick@visualchas.com> wrote in message
news:aRYF7.10860$Y6.658050@news1.rdc1.ct.home.com...
> Hello,
>
> I remember reading a technical aritcle referring to printing to a
multiport
> lexmark print server.  I believe it said to setup the printers using rlp
and
> naming to printers lexmark0, lexmark1, etc.  Can anyone tell me how to
setup
> a multiport jetdirect (500x) for example.  Is it as simple as the lexmark
> situation?
>
> Thank you very much,
> Nick

There are several ways to go about this, and only because I don't see anyone
else answering, I will describe what I do.
If someone comes along later and gives other advice decribing how to use
netcat instead of lpd, depending on who it is I highly recommend taking it.
However, I have never bothered to set up a netcat based printer interface
script, and I do use lpd all the time and it does work great for me so far,
so I give the only example I can say from personal experience works.

get the following file:
http://www.aljex.com/bkw/sco/add_lpd.ksh
and stick it in your path and chmod 755 it, or just run it manually from the
current directory wherever you download it to by doing "ksh ./add_lpd.ksh"
(when it comes time to run it...)

you can run it without options to see some help.

telnet to the IP of the jetdirect and use the menus to enable tcp/ip, you
may need to use the windows jetadmin software to give the print server an IP
in the first place, before you can telnet to it. If so, then you can also
just set the option using the windows program and there is no real reason to
telnet to it.

enable "tcp/ip" which really means "enable the lpd protocol" but it doesn't
say so.
give the print server an IP that is part of your local net
turn off banners in the print server

edit /etc/hosts on the unix box, add a line like this for the print servers
ip
assuming (for example) if the printer is in accounting, and it's the first
print server in the accounting dept, and it's IP is 10.0.0.105. the hostname
is something you invent, accounting_ps1 is just my particular naming
convention.

10.0.0.105  accounting_ps1

next you need to find out the names of the queues for the different ports in
the print server. I have a few common examples documented in the help for
add_lpd, and in your case I happen to know that the que names are "raw1,
raw2, raw3" and "text1, text2, text3". the raw ports pass all data as-is,
the text ports will insert carriage-returns with every line-ending.

think up name(s) for the new printer(s), I like to go ahead and configure
all the available ports even if there is only a printer on one port at
first. then you can add printers to the ports and use them immediately later
on without remembering this stuff your doing now. so I would use "acct1,
acct2, and acct3"

now you are ready to actually install the printer in unix using add_lpd

the syntax is
add_lpd.ksh <new local printer name> <remote server name> <remote port name>

an example using above example names, to set up all three ports would be:

ksh ./add_lpd.ksh acct1 accounting_ps1 raw1
ksh ./add_lpd.ksh acct2 accounting_ps1 raw2
ksh ./add_lpd.ksh acct3 accounting_ps1 raw3

you can test the new printer immediately, but the script actually includes a
test already.
if you get a sheet of paper on the new printer saying "printer ____ added
sucessfully..." then you are done.
you may need to run "scoadmin printer" to turn off banners from unix (not to
be confused with banners that may come from the print server itself.

note, simple direct remote lpd printers like this do not filter the data
through a printer interface script like all the other printers, even though
an interface does get created. If you need an interface script, you can set
up a "local printer" that has /dev/null as it's device, and in it's
interface script you actually send the data into "lp -dacct1 " instead of a
real device. this is called a virtual local printer or a wrapper. Tony
Lawrence has instructions on his site for setting it up.
Some of the things you would normally modify an interface script for, can be
handled in /etc/printcap and/or in the print server for remote lpd printers,
so you may not need to set up a wrapper virtual printer.

--
Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani

Take Control of Maintaining Your Mac

Take Control of Syncing Data in Leopard

Take Control of Upgrading to Snow Leopard

Take Control of Buying a Mac

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.