I guess the question in my mind is: do you need a GUI or not? If you don't need a GUI, then you need some kind of terminal emulator that understands SSH on the Windows boxen, or something like HostOnDemand that runs in a browser and downloads the terminal emulator when needed.
If you do need a GUI (and with a COBOL back end, why?), then you need either a VNC client or an X server on the Windows machines. If VNC, then you can use the browser-based VNC client on port 5900 (which will eat CPU like crazy on the mainframe side) or you have to install something on the Windows boxen that understands X. There are browser-based X servers (remember, with X, the SERVER runs on the Windows workstation), but they're all slow and somewhat management intensive (as well as being CPU hogs). The VNC client is a little friendlier in terms of network bandwidth than X, especially if you have limited bandwidth to the client. A native SSH client like PuTTY would be even lighter weight, although you get the fun of deploying it. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
