Xref: utzoo comp.protocols.tcp-ip:3863 comp.dcom.lans:1489 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ncar!boulder!spot!ziel From: ziel@spot.Colorado.EDU (ZIEL FRED ADAM) Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans Subject: Print Server Message-ID: <6770@sigi.Colorado.EDU> Date: 22 Jun 88 06:51:53 GMT Sender: news@sigi.Colorado.EDU Reply-To: ziel@spot.Colorado.EDU (ZIEL FRED ADAM) Organization: University of Colorado, Boulder Lines: 18 The architecture we are trying to test is more ideally implemented with independently adressable network devices, so I'm looking for a (hopefully cost effective) way of putting our printers on our ethernet network instead of hanging them off of a server. It sounds like we need some of the functionality of a cisco terminal server, but that looks to be a bit of overkill. Something similar was described in Comp.newprod from Excelan a few weeks ago. We would also like some method of having the tape drive be an independent device, but I think that is less important at the moment. I would appreciate any info (esp. pricing) on the minimum cisco or Excelan systems. I would also appreciate any suggested alternatives or problems with what we're trying to do. If I get enough (any :-) replies, I will post a summary. Thanks. ---------------------------------------------------------------------- Fred Ziel, Colorado Center for Astrodynamics Reserach, CU-Boulder uucp: ..!{nbires,ames!ncar}!boulder!ziel domain: ziel@spot.colorado.edu disclaimer.h (line 10): syntax error.