Anybody else have any ideas?

Sheesh....where to start???

Using a dumb terminal has nothing to do with networks at all. And a dumb terminal isn't "remote". It is local, even if it's on a different continent. The kernel will be talking to a tty device on the local computer. This device will be connected by a cable to dumb terminal or a modem. But the tty device (or serial port) is local. It will have a name in /dev. Maybe /dev/tty01 or something.

I have never done this under Linux. Under HP-UX you use getty while under Solaris, it's ttymon. It's amazing that this thread got this long without anyone mentioning which distro of Linux. But looking at redhat 7.2, I find several things by typing "man -k getty". "man agetty" looks promising. Maybe that would be a place to start. And why not mention your distro to save some time if a linux expert shows up?

Yes, I understand that it is not network. I was just saying that I have a special hub like thing that allows the serial connection to go over a cat5 cable so that you can add many terminals to the single server without adding more ports serial ports. I have tried getty however, it also didn't seem to "find" (?) the terminals. Using red hat 8.0

Okay, that whole thing with the networking and all just confused everybody. Let me make this a bit more simple to understand. From the top: I have a server that is running Red Hat Linux 8.0. The server has two serial connection ports. The server does not have any other software specific to Wyse terminals. Only the standard stuff that comes with the distro is installed. I have one terminal that has been connected to the serial port via the serial port on the terminal. Now when I turn on the terminal and boot up the server all that happens is that random symbols and such appear on the terminal. I have tried messing with VT types and getty. I do not know much about these dumb terminals, but always thought that TERM, and getty would detect that it was a tty connection and just send the login prompt. The terminals are Wyse wy-60s located here: http://www.wyse.com/service/discontd/terminals/wy60.htm And, yes i have been through their knowledge base alot.

Hope this helps some, and thanks for your time!

sorry i just wanted to help ... wont happen again

asked my web server teacher today and he said somthing about you need to install somthing like ssh and make sure its communicating on a protocol like netboui or tcp/ip he also mentioned somthing about the /dev folder and having a shared file in it.

Thanks for the attempt and the effort jhoffman, but it has nothing to do with networking As we have been trying to show, it is done locally with serial connection. What I was talking about with the networking was I had a way to bridge the serial connection over ethernet, however when it connects back to the server it is done with a serial connection not ethernet.

I guess my question should be: How to set up a Wyse dumb terminal?