Our Latest Posts: -
Passive Income Smooths the Flow -
Hitting the Google Sweet Spot -
Vista Boomers - Microsoft's Power Failure -
Book Review: Programming in Objective-C 2.0 (Second Edition) Translators wanted!
Best of the Newsgroups: printing to D-Link DP-300U
What is this stuff?
Main Index
From: "Brian K. White" <br...@aljex.com>
Subject: Re: Print Server Port Numbers?
Date: Mon, 15 Sep 2008 21:47:57 -0400
Message-ID: <C592F71450994B54B7D92E7D2FE438FE@miata>
References: <48cde989.20027890@news.chi.sbcglobal.net> <mailman.0.1221494292.12960.sco-misc@lists.celestial.com> <48ce8d7e$0$2923$fa0fcedb@news.zen.co.uk>
>> On Mon, Sep 15, 2008, RWP wrote:
>>> Does anyone know what port number(s) D-Link's DP-300U print server
>>> uses to print on each of it's three pirnter ports? I need them for
>>> netcat printing.
Why do you assume there even IS any raw tcp feature?
The dlink web site and some user reviews on shopping site both imply that it
supports LPD and neither mentions raw tcp on any port nor uses the term
jetdirect anywhere.
Based on the <a
href="ftp://ftp.dlink.com/Printserver/dp300U/QIG/DP300U_QIG_100.zip">documentation</a>
I'd just use LPD.
And from that same document, apparently you should point a browser at the
devices ip and go to the lpr setup page to find out (or define your own) the
port names to use as lpd/lpr queue names.
IE: for parallel port 1, it might be
echo this is a test |rlpr -P PS-1123D6...@192.168.0.20
You can use the native lpr support in sco, except you lose the use of
printer interface scripts then, unless you set up dummy loopback or
lp-wrapper printers as described in a few articles on pcunix.com
Personally I only ever use this:
http://www.aljex.com/bkw/sco/#rlpnc
and this with it.
http://www.aljex.com/bkw/sco/#rlpr
The first provides a convenient way to use netcat and rlpr, and includes
netcat already, in an out of the way place thet the included printer model
script expects, but which won't clobber or interfer with any other netcat
binary you may already have.
The second adds rlpr as a seperate package that the first is already
prepared to use.
Basically just unpack the two tars, create printer(s) in scoadmin using
device /dev/null and model Net, and edit a line in /etc/printers where the
first field is the same as the name of the Net printer.
In your case it would look like:
If the printer is named "accounting", the DP300U's IP is 192.160.0.20, and
the printer is on parallel 1
accounting:192.168.0.20:PS-1123D6-P1:rlpr:HPLaserJet:comments...
comments should be info about printer model, print server model, physical
port, mac address, etc...
You'll probably need to mark the model scripts executable before the Net
model will work, since it works by just running one of the other model
scripts in-place instead of by having you copy and edit it.
chmod 755 /usr/spool/lp/model/*
You may also want to mark the rlpr binary suid so that is has permission to
access priviledged tcp ports.
chmod +s /usr/local/bin/rlpr
The advantage here is that, unlike using the native lpr support, the
resulting printer is just like an ordinary local printer.
You get the use of printer interface scripts just like usual, any printer
interface script, not just one you hand-edit to insert netcat functionality,
and you get it without having to set up two printers in the OS for every
real printer. (an lpr printer which can't use an interface script, and a
wrapper lp-to-lp printer that provides the interface script) You never copy
or edit any scripts. You just define a printer in scoadmin and edit or
create a line in a config file. Also, thereafter, when that printer changes
ip or connection type or even interface script (model) , you just edit the
config line and the change takes effect with the very next print job, no
restarting anything or even going into scoadmin.
--
Brian K. White br...@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
Add your comments