Xref: utzoo comp.dcom.sys.cisco:907 comp.dcom.lans:7418 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!convex!pat From: pat@convex.com (Pat Peters) Newsgroups: comp.dcom.sys.cisco,comp.dcom.lans Subject: unusual terminal server need Message-ID: <1991Mar08.003144.12983@convex.com> Date: 8 Mar 91 00:31:44 GMT Followup-To: poster Organization: Convex Computer Corporation, Richardson, Tx. Lines: 34 We have an unusual situation that I'd like to user a terminal server for. I'm interested in opinions on which terminals servers might be able to accomplish what I want to do. We have quite a few machines in our lab. Using a lab machine requires connection to the consoles (there are two) via RS-232. However, you can do lots of work without ever being in the physical presence of the machine. Right now we've run serial connections to some async ports on a time sharing machine and you can use tip, kermit, etc. to get your hands on the consoles without having to visit the lab. You can be in your office and use your workstation, which is a much more comfortable and productive environment for many people. Nice as this is for the users, it's a pain for the sys admins. If someone wants to use a particular lab machine via tip, they have to have a user id on the machine that has its console connections. We also get to string lots of serial cable from the lab into the computer room. It's ugly, it's inflexible, there's got to be a better way. What we really want to do is hook up the console ports to a terminal server and have people telnet/rlogin to the terminal server and then come out through the serial ports--exactly the reverse of how you'd normally use a terminal server. I'm told that most terminal servers don't have the ability to accept incoming telnet/rlogin sessions in the quantity necessary to make this viable. Anyone out there have some suggestions? Thanks -- Pat Peters Convex Computer Corporation UUCP: pat@convex.com 3000 Waterview Pkwy Richardson, TX 75080 Voice: (214) 497-4706