Now I would like to set it up to work in Openserver 5.0.6. I have browsed
some Internet newsgroup and SCO resource sites. It seems that 'netscat' is
highly recommended for this purpose. The SCO box has already another non-HP
network printer running. But it is configured as a local printer without
using 'netcat'. I would like to set it up the same way.
In the interfaces folder, the existing non-HP printer has the following in
the end of the printer file:
# ======================================================
# Reset printer to PCL mode
case "$format" in
HPGL2)
echo "\033%1A\c";;
HPGL2_P)
echo "\033%1A\c";;
PS)
echo "\033%-12345X@PJL enter language=pcl";;
*) ;;
esac
) | rcmd microplex lp -dprinter1
# =======================================================
Apparently, it is not using netcat but rather, it runs 'rcmd' and direct to
the destination printer server microplex. I am not sure how it works but
the printer is working fine in SCO. If I have the IP address and port
number of the printer server, can I set up the printer as local without
using netcat?
Joe
It depends on the print server.
By the looks of that command however, it looks more like the existing 'print
server' is a full server of some description (either a Unix box or a Linux
box). Print Server's don't support remote commands, let alone issuing 'lp'
commands to them.
If you do not wish to use 'netcat', look to see if your un-named print server
supports 'RLP' (or Unix Remote Printing). If so, 'mkdev rlp', and do it that
way.
But I'd strongly suggest you do use 'netcat'.
bkx
>I have a new multi-function copier that has a built in print server
>configured for TCP/IP printing. I have it configured in Windows to run
>print jobs.
All multifunction copiers are created equal. However, many of them do
not support HP Jetdirect emulation on port 9100. I'll assume your
reason for *NOT* using netcat is that your unspecified
multi-malfunction copier does not have this feature. Many such print
servers claim Unix support, which really means LPR/LPD. Unless your
unspecified copier has HP JetDirect emulation or can accept printing
data directly to an IP socket, netcat will not work.
>Now I would like to set it up to work in Openserver 5.0.6. I have browsed
>some Internet newsgroup and SCO resource sites. It seems that 'netscat' is
It's netcat, not netscat.
>highly recommended for this purpose. The SCO box has already another non-HP
>network printer running.
All non-HP network printers are created equal. I assume that the
reason it's setup this way is that the unspecified version of the
MicroPlex print server has said printer directly attached and that
rcmd was used to get print spooler support.
>) | rcmd microplex lp -dprinter1
Methinks it should be:
| rcmd microplex "lp -dprinter1"
but might work as is. The device named "microplex" has a directly
attached printer, or an additional remote print server, attached,
named "printer1". Some clue as to the topology (wiring and
configuration) of this pretzel might be helpful. Is it this one?
http://www.microplex.com/info/m305ds.pdf
According to the data sheet, using rcmd (rsh, etc) is the prefered way
of printing. However, it does have LPR/LPD capabilities.
>Apparently, it is not using netcat but rather, it runs 'rcmd' and direct to
>the destination printer server microplex. I am not sure how it works but
>the printer is working fine in SCO. If I have the IP address and port
>number of the printer server, can I set up the printer as local without
>using netcat?
Yep. Netcat will NOT work. Use LPR/LPD as in "mkdev rlp" to
configure. Use:
rlpstat printer_name
for status info. The problem with LPR/LPD is that is has no support
for printer scripts. (There was a method of providing spooler script
support to LPR/LPD posted in this newsgroup but I can't find it). The
reason someone setup printing using rcmd was to get spooler script
support.
--
Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
(831)421-6491 pgr (831)336-2558 home
http://www.LearnByDestroying.com WB6SSY
je...@comix.santa-cruz.ca.us je...@cruzio.com
It's a Panasonic multifunction unit, documentation is poorly written. I am
not positive that it would support RLP. I have downloaded netcat and tried
to test it with my hp laser connected to an Intel print server. This
printer has been working okay in SCO because I installed it using the
proinstall program from Intel. I don't want to make sure it works before
using with the Panasonic. To test it, I have done the following:
1. install a new printer laser1 with 'scoadmin printer' and set up to use
/dev/null
2. in the interfaces folder, the file laser1 is as follows:
PATH="/bin:/usr/bin:/usr/lib:/u/bin"
export PATH
printer=`basename $0`
request=$1
name=$2
title=$3
copies=$4
options=$5
shift; shift; shift; shift; shift
# Look for HOST and Port address
if [ $? = 0 ]
then
PRTHOST="hp6l"
PRTPORT="3001"
else
exit 1
fi
(
files="$*"
i=1
copies=1
while [ $i -le $copies ]
do
for file in $files
do
cat $file | /usr/lib/lponlcr
echo "\033E\c" # may need change for Lexmark
done
i=`expr $i + 1`
done
)|netcat -d -h $PRTHOST -p $PRTPORT
3. Nothing got printed. But I can get something with this:
cal | netcat -d -h laser1 -p 3001
although I have lines like staircases and some characters are missing.
I have to get the Intel to works before testing the Panasonic. I am sure
that I have some missing pieces.
Joe
Umm.. given that you've set 'PRTHOST' to be 'hp6l', I'm assuming the test you
did was actually 'cal | netcat -d -h hp6l -p 3001' ?
In any case I'm picking your interface script is a little off. The 'port'
will *NOT* be passed to it from lp. you will need to hard-wire this.
The host name won't be either. You might want to use something like:
PRTHOST=`basename $0`
As i'm assuming the printer name is the same as a host.
Just a thought.
bkx
Add set -x to the following and then check root's e-mail after
you submit a job. The -x output will be returned as e-mail taking
the response as a failure. Examine the mail and see if it tells you why
the job is failing
Change that to: cal | xtod | netcat -d -h laser1 -p 3001
and see if that doesn't get rid of the stair-step.
Based upon you above statement about lines like staircases, I'd say
that netcat to port 3001 is working. You need only find out why your
interface script is failing. Try adding the "set -x" at the beginning
of the script and then check the e-mail response to the next print job.
>
> I have to get the Intel to works before testing the Panasonic. I am sure
> that I have some missing pieces.
Getting the Intel working is no guarantee that the Panasonic will work
with netcat. As other posters have pointed out, some print servers will
not accept a port connection that netcat needs to work.
>
> Joe
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
>3. Nothing got printed. But I can get something with this:
> cal | netcat -d -h laser1 -p 3001
> although I have lines like staircases and some characters are missing.
Try:
cal | /usr/lib/lponlcr | netcat -h laser1 -p 3001
See command line examples at bottom of:
http://www.LearnByDestroying.com/sco/lp/netcat.txt
The IP address of "laser1" must be defined in:
/etc/hosts
So fix the staircase:
http://aplawrence.com/SCOFAQ/scotec7.html#staircase
And get rid of the -d, yopu don't need it for this.
--
Tony Lawrence
Free SCO, Mac OS X and Linux Skills Tests:
http://aplawrence.com/skillstest.html
Thanks so much. It's fixed. Also, I found I made a mistake with the path.
Now I can get it to work with my Intel print server.
Joe
"Jeff Liebermann" <je...@comix.santa-cruz.ca.us> wrote in message
news:7l6n2v8ui98vi02f9...@4ax.com...
>Jeff,
Yes?
>Thanks so much. It's fixed. Also, I found I made a mistake with the path.
>Now I can get it to work with my Intel print server.
Ummm...
http://www.tkrh.demon.co.uk/netport.html
http://www.aplawrence.com/Reviews/netport.html
http://www.aplawrence.com/SCOFAQ/scotec7.html#getnetcat
There is a email sent to root regarding an lp error. It complained about
the path to netcat. I copied the file to /etc and then changed the last
line of the printer script file to:
)|/etc/netcat -d -h $PRTHOST -p $PRTPORT
Alternatively, I should copy netcat to /usr/bin, which is defined in the
path.
Now the Intel print server works, but I have to go back to the Panasonic
DP-6010, which I have done some tests without any success. I followed the
same procedure as I did with the Intel Netport:
1. create a hosts entry for the printer
2. create a printer with output device of /dev/null
3. identify the printer port of the device
In Windows, I have the printer installed by configuring TCP/IP printing
and print using lpr mode instead of raw. Using netstat, I found that
Windows was communicating with port 515 of the device. In SCO, I tried to
connect to the printer using netcat:
# netcat -d -h panasonic -p515
Host: pan6010
Port: 515
gethostbyname(pan6010)=0x804cb28
ip = 192.168.0.45
socket()=3
connect()=0
>
4. put the following printer script in the interfaces directory
PATH="/bin:/usr/bin:/usr/lib:/u/bin"
export PATH
printer=`basename $0`
request=$1
name=$2
title=$3
copies=$4
options=$5
shift; shift; shift; shift; shift
PRTHOST="panasonic"
PRTPORT="515"
(
files="$*"
i=1
copies=1
while [ $i -le $copies ]
do
for file in $files
do
cat $file | /usr/lib/lponlcr
echo "\033E\c" # may need change for Lexmark
done
i=`expr $i + 1`
done
)|/etc/netcat -h $PRTHOST -p $PRTPORT
However, I cannot get it to print by using netcat directly or lp to it. I
was told that the printer support lpr/lpd, maybe I have to set it up as a
remote printer.
Joe
>There is a email sent to root regarding an lp error. It complained about
>the path to netcat.
The first 10 commandments have already been taken. Number 11 should
be: "Thou shalt not paraphrase or abrev thy error messages".
>I copied the file to /etc and then changed the last
>line of the printer script file to:
>
> )|/etc/netcat -d -h $PRTHOST -p $PRTPORT
Remove the -d (for debug) and things might work a bit better.
>Alternatively, I should copy netcat to /usr/bin, which is defined in the
>path.
Depending on the background program, the default path varies from
zilch to some collection defined in some config file. In any case,
the administrative programs in /etc should never be on a default path
unless you enjoy blundering into trojan horses.
>Now the Intel print server works, but I have to go back to the Panasonic
>DP-6010, which I have done some tests without any success.
Ok. I give up. Please seperate the problems getting these two print
servers working as I get easily confused when you switch back and
forth in one sentence.
>I followed the
>same procedure as I did with the Intel Netport:
>
>1. create a hosts entry for the printer
>2. create a printer with output device of /dev/null
>3. identify the printer port of the device
> In Windows, I have the printer installed by configuring TCP/IP printing
>and print using lpr mode instead of raw.
All versions of Windoze are created equal. I bet you didn't know
that. Since you manage to configure tcp/ip printing in Windoze, my
guess is that you have Windoze 2000 or XP which have this built in as
"print to a standard port". You have two choices when you do this.
One is LPR/LPD which uses port 515. The other is for HP JetDirect
emulation, which is on port 9100. You can switch back and forth
between these two using the printers properties. Turn *OFF* the
"advanced features" check box as this causes problems.
>Using netstat, I found that
>Windows was communicating with port 515 of the device. In SCO, I tried to
>connect to the printer using netcat:
>
> # netcat -d -h panasonic -p515
Won't work. Port 515 is specific to the LPR/LPD protocol. You can't
just dump output to port 515 and expect anything to print. There's a
complex RFC describing the ordeal process required to get LPR/LPD to
print.
You might wanna disclose whether your Panasonic print server includes
JetDirect emulation. If so, use port 9100. If the port is something
else, I would be interested in knowing the port number so I can add it
to my chart.
>However, I cannot get it to print by using netcat directly or lp to it. I
>was told that the printer support lpr/lpd, maybe I have to set it up as a
>remote printer.
Yep. Maybe.
Thanks for following up the thread.
> Remove the -d (for debug) and things might work a bit better.
Absolutely, I should not have left it in the printer script.
> You might wanna disclose whether your Panasonic print server includes
> JetDirect emulation. If so, use port 9100. If the port is something
> else, I would be interested in knowing the port number so I can add it
> to my chart.
The technical guy from the vendor told me that it did not support JetAdmin
emulation. He came in today and set it up as a remote printer. It worked.
He knew nothing about SCO but he knew that it worked with lpr/lpd.
I have tried connecting to port 9100 using netcat. It failed. For now, I
can only connect to port 515. Well, I have to leave it as a remote printer.
No choice.
Thanks, Jeff.
Joe