Fog Creek Software
Discussion Board




Favorite telnet client for Win32

What's the best telnet client for Win32?

Jeff
Saturday, February 22, 2003

My two favorites are Tera Term and PuTTY. Tera Term looks more "polished" but PuTTY has better support for class UNIX control characters. Both have add-ons that can do SSH also.

Dan Maas
Saturday, February 22, 2003

dtelnet, very small and simple.

http://dtelnet.sourceforge.net/

T
Saturday, February 22, 2003

My vote goes to putty, especially because it supports ssh and ssh2.

Jan Derk
Saturday, February 22, 2003

PuTTY is what I use. I wouldnt go back.

Its small, efficient, one EXE @ 350K, supports ssh, and telnet, and even rlogin, so it pretty much covers your needs in the area.

Patrik
Saturday, February 22, 2003

Yep, can't really go past PuTTy

Damian
Saturday, February 22, 2003

I've used PuTTY for ssh (secure shell), but I've used eXceed for everything else. 

Bella
Saturday, February 22, 2003

Nobody uses WinCRT any more?

For a long time that was the gold standard...

Joel Spolsky
Saturday, February 22, 2003

secureCRT

Daniel Shchyokin
Saturday, February 22, 2003

Putty. Definitely.

Ros
Saturday, February 22, 2003

rxvt/OpenSSH from cygwin.

There's no excuse (or good reason) to be using telnet in the year 2003. Unencrypted network logins suck.

--
Alex Russell
alex@netWindows.org
http://www.netWindows.org

Alex Russell
Saturday, February 22, 2003

putty is great, but WinCVS needs a COMMAND LINE ssh, which putty doesn't support (not that I know of).  I am forced to use TWO terminal clients, putty and SecureCRT. 

Vincent Marquez
Sunday, February 23, 2003

You could set Putty to forward the CVS port from the remote machine to localhost and point WinCVS at that.

That works for me with TortoiseCVS anyway.

Neil E
Sunday, February 23, 2003

Yep port forwarding is great. It makes anything (ftp, http, pop, etc) secure.

I don't use it myself, but if you want a command line interface to Putty use PLink. The Putty manual even contains a topic about how to use PLink with WinCVS:

http://the.earth.li/~sgtatham/putty/0.53b/htmldoc/Chapter7.html#7.5

Jan Derk
Sunday, February 23, 2003

Don't forget all the Macros you can create with eXceed.  auto-login, etc

Bella
Sunday, February 23, 2003

Another vote for putty and the related goodies (pscp, etc).  Very slick.

Rodger Donaldson
Sunday, February 23, 2003

Vincent,

Have you looked at plink from the putty distribution?

Chris Blaise
Sunday, February 23, 2003

Microsoft Telnet

Just kidding.  Putty.

We build great Operating systems, database servers, development tools, etc.  Give you a decent telnet client.  Hell No!

Cedric
Sunday, February 23, 2003

Putty all the way!!!!!!!!!

JD

JD
Monday, February 24, 2003

"There's no excuse (or good reason) to be using telnet in the year 2003. Unencrypted network logins suck."

Not all information is sensitive.

Not all information is on a breachable network.

Telnet isn't just about remote logins; it is an effective tool for developers creating trivial tcp-based protocols.

And most of the telnet clients mentioned in this thread support secure logins (ssh etc).

Nice
Monday, February 24, 2003

[but WinCVS needs a COMMAND LINE ssh]

Another poster pointed out plink.  Plink, the command-line SSH client in the PuTTY distribution, works very well for CVS / WinCVS over SSH.

Kyle Cordes
Tuesday, February 25, 2003

Vincent,

have a look at https://sourceforge.net/docman/display_doc.php?docid=766&group_id=1 for a detailed explanation of using WinCVS with Putty and Plink.

Just me (Sir to you)
Friday, February 28, 2003

Kermit 95. I must admit that I haven't tried its SSH features, but like its scripting.
See:

        http://www.columbia.edu/kermit/k95.html

Jimmy Burgett
Monday, March 03, 2003

problems with putty:

- can't store settings in a file at the time of writing; uses registry
- personally I can't get the F keys working

jago25_98
Saturday, May 08, 2004

Did anyone try out IVT?

lleroy
Wednesday, May 12, 2004

*  Recent Topics

*  Fog Creek Home