shaver@atanasoff.cs.iastate.edu (Dave Shaver) (01/20/89)
We have one host here in the department that we can't hookup to our
LAN. (Our LAN consists mostly of VAXen, Suns, etc). One solution we
have come up with is to purchase a LAN terminal server and hook the
ports on it to this non-LANed host.
We'd like to be able to use telnet to connect to these ports connected
to the terminal server. The server would translate the telnet session
to the host via the serial ports. Thus, on the LAN side, it looks like
a normal telnet session. On the host side, it looks like a normal
hard-wired terminal session.
We plan to one day junk this host, so we'd like to have the option of
hooking up normal ASCII terminals to this server at a later time. The
idea being that users could sit at the server and give the (IP) address
of the host they want to talk with and it would start a telnet
session. (I assume this is the original intent of most ``terminal
servers'' out there.) Thus, if possible, this server must do
bidirectional telnet sessions.
So, enough background. There are several companies that make boxes
somewhat like this. We're looking for comments on ANY terminal
servers. Good, bad, or otherwise. We're also open to other ideas on
how to get this host onto the LAN. If the box doesn't speak telnet,
we'd also be open to anything else.
Please MAIL responses and I'll summarize for the net. Thanks in
advance for your time and comments/ideas. (Please let me know in your
mail if I may include your name in the summary.)
Cheers,
/\ Dave Shaver -=*=- CS Systems Support Group, Iowa State University
\\ UUCP: {hplabs!hp-lsd,uunet!umix!sharkey}!atanasoff!shaver
\/ Internet: shaver@atanasoff.cs.iastate.eduron@hardees.rutgers.edu (Ron Natalie) (01/22/89)
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