Windows as Unix "dumb" terminal

[ZazuMC]

Now, obviously it wouldn't be a dumb terminal, but here is my situation. I've got a client that has a Unix server and is running a couple of dumb terminals. They have a need to add two more terminals, but they also plan to upgrade to a Windows based solution in the not too distant future (yes, do away with the Unix server).

My question is, what would be my most logical route to take to add two more terminals (dumb or otherwise) without my client spending the money on them, and then have to turn around and spend more money on Windows systems (to replace the terminals) in the next year (or less)?

I'm thinking a W2K system connecting to the Unix server using Hyperterminal or a telnet session would work fine, but I may be mistaken. I'm not a Unix guy, so please forgive me for being a little in the dark here.

Thanks in advance!!

 

[sleipnir214]

Something similar to hyperterminal or telnet is all you need. But I would go with something a little more featureful and the basic telnet or hyperterminal. Some unix-based terminal applications require specific terminal emulations to work correctly.

CRT by VanDyke Technologies runs on Win32 and will do pretty much everything you want.

If you require a higher-level of security (ssh versus telnet, for example), then SecureCRT by the same company is a good product. As a general rule, I recommend ssh over telnet.

Want the best answers? Ask the best questions:

http://www.catb.org/~esr/faqs/smart-questions.html

TANSTAAFL!

 

[olded]

Hi:

There's tons of terminal emualtion software out there. I like CRT - its a good product.

Another good product (2nd to CRT) is Tiny TERM or it's big brother, TERM, from Century Software.

http://www.censoft.com.

Regards,

Ed

 

[edfair]

If the user is running out of tty ports the telnet is logical if there is already a network in place.
And even if there is no network, the network money would be shifted to current from future where the serial would be trashbinned.

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[fredericofonseca]

If your system has TCP/IP installed or can have without more expenses (you did not mention the Unix version), then I would advise to get one of the many Emulators outhere that work over TCP/IP. If it doesn't then you will need to have enough serial ports available on the Unix side.

Here is a link with a lot of possible emulators.

http://aplawrence.com/SCOFAQ/FAQ_winterm.html

some of then really good and cheap.

I Would not use hyperterminal or windows telnet for anything though.

 

[ZazuMC]

Thanks to all of you for the suggestions. The systems are already networked over TCP/IP, so the networking part of it is already there - just plug it and go (well, of course there's a little more than that, but you know what I mean ;-). I knew there was a lot of emulation software out there, was just using Telnet and Hyperterminal as examples and making sure there really wasn't much more to it than that.

My biggest focus is getting them to where they are able to go "seamlessly" from a Unix server to a Win2K (or Windows 2003) server in the next year or so. I didn't want to recommend that they spend the $250 - $450 on a dumb terminal when they would be just as well off spending $700 or so on a new PC running windows that will work both now and later. I needed to be sure that a Term Emulator program will do what they need. I have since found out that they are running an emulation program on a couple of other PC's - guess I should have checked that first huh ;-)

Anyway, thanks again for the info and suggestions. It was all very helpful!