Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!apple!sun-barr!newstop!texsun!pollux!smu.edu!merlin
From: merlin@smu.edu (David Hayes)
Newsgroups: comp.protocols.tcp-ip
Subject: TCP/IP Terminal Servers
Message-ID: <15973@pollux.UUCP>
Date: 20 Oct 89 19:44:44 GMT
Sender: news@pollux.UUCP
Reply-To: merlin@smu.edu (David Hayes)
Organization: Southern Methodist University, CSE Dept. Dallas, TX
Lines: 23

SMU is looking for recommendations on terminal servers.
The units must speak TCP/IP, but DEC LAT protocol would be
a help, also.  We want 48 ports total, in one or more units.
Modem control on these ports would be valuable, but is
not strictly required.

I'm particularly concerned that the host computers be able to
contact an output device, such as a printer, connected to one
of these terminal server ports.  I've no idea how this is
accomplished under TCP/IP.  Our workstations don't have enough
serial ports for all our printers, though, so we need to be
able to do this.

I'd appreciate any recommendations or experiences you want
to share.  I've already got cisco routers, so I'd lean towards
cisco terminal servers if all other considerations were equal.
I'm also thinking about Annex, Bridge, and DEC devices, though.
Please let me know how you're solving these problems,


David Hayes	School of Engineering	Southern Methodist University
merlin@smu.edu	uunet!smu!merlin
"Argue for your limitation, and, sure enough, they're yours." - Richard Bach