[comp.protocols.tcp-ip] Network Printing

hughes@silver.bacs.indiana.edu (08/03/89)

We have a need at Indiana University to implement a TCP/IP-based
network printing system for our statewide network.  Such printing
services must be made available to a mixed and wide variety of
vendor's machines and operating systems (with the common denominator
being, again, TCP/IP).  Included in this mix are VAXes and MicroVAXes
running VMS (with Wollongong's product), ULTRIX, and Berkely 4.3; 
IBM mainframes; Sun, NeXT, and Apollo workstations; and a few others 
to boot.  (Support for PC's and Mac's would be nice too...)

We know about the LPR capabilities under most UNIX implementations
(and coming in the next release of Wollongong), and have been using
it in a few places on the net.  But does the collective family
of LPR/LPD/LPQ/LPC/LPRM provide enough functionality *and* reliability
to satisfy most users (and implementors) for such a large base?  And 
is the maintenance of dozens or hundreds of local printcap files an
administrator's nightmare?

And if this seems to be the most viable solution, is anyone
aware of enhancements to this suite, possibly developed at 
another university (or even available commercially), that we 
might be interested in?  

Any information at all would be appreciated and investigated.

Please respond via email.  I will post a summary of solutions
if so requested.  Thanks in advance.

          =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
               Larry Hughes, Senior Programmer
                University Computing Services
               Indiana University, Bloomington

          Internet: hughes@jade.bacs.indiana.edu
                    hughes@silver.bacs.indiana.edu
          Bitnet  : hughes@iubacs
          =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

nelson@sun.soe.clarkson.edu (Russ Nelson) (08/03/89)

In article <44500002@silver> hughes@silver.bacs.indiana.edu writes:

   ... But does the collective family
   of LPR/LPD/LPQ/LPC/LPRM provide enough functionality *and* reliability
   to satisfy most users (and implementors) for such a large base?

*and* security?  The problem we have here is charging users for the printing
that they do.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])|(70441.205@compuserve.com)|
       (Russell.Nelson@f360.n260.z1.fidonet.org)|(BH01@GEnie.com :-)

melanie@uxe.cso.uiuc.edu (08/05/89)

the university of illinois has a distributed printing system. a central
server resides on a vax 3500 and talks to satellite servers and/or clients
on suns, vaxes, convexes (convi?) and an ibm 3081. this is all tcp-based.
however, since the 3500 runs ultrix and decnet-ultrix, a decnet interface
could be written in a straightforward fashion. 

accounting cards (well, theyre virtual...) are cut to the ibm-based
accounting system by the central server (co). chargeback is quite accurate.

i didnt write it, i just use it...

contact

charley kline
sr research programmer and resident network guru
kline@tuna.cso.uiuc.edu

or 

sue greenberg 
charley's boss
sue@uxh.cso.uiuc.edu