Xref: utzoo comp.dcom.lans:2295 comp.protocols.tcp-ip:6001
Path: utzoo!attcan!uunet!husc6!bloom-beacon!apple!rutgers!elbereth.rutgers.edu!hardees.rutgers.edu!ron
From: ron@hardees.rutgers.edu (Ron Natalie)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: Looking for information on LAN terminal servers (dumb host <=> LAN)
Keywords: LAN terminal server
Message-ID: <Jan.22.10.06.15.1989.3558@hardees.rutgers.edu>
Date: 22 Jan 89 15:06:16 GMT
References: <708@atanasoff.cs.iastate.edu>
Distribution: na
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 15

I'd recommend CISCO for the "milking machine" application.  We have a
CPU (it's a COMTEN front end to an IBM) that is a real bear.  Chuck Hedrick
spent a lot of time fine tuning the telnet server in the CISCO to make it
work well when milking.  In addition, he's put out some new TELNET options
to make milking more palatable when going from TERMINAL->SERVER->TERMINAL.

Configuring of the lines on the Cisco is straight forward and the modem
control signals are handled properly so that when the host hangs up the
connection goes away and when the connection goes away the host sees
"carrier" drop.  Cisco also allows a rotary to be bound to a different
address than the server so you can treat the rotary as a host in itself
rather than having to telnet to the server and then select or using funny
TCP ports.

-Ron