The Windows analogue to SSH is Terminal Service.
There are other remote desktop thingys (PcAnywhere, VNC, etc), but they suck in comparison, being slow and flaky. TS is snappy and on a LAN it almost feels like a local computer.
The most annoying thing with TS is that there is no built in way to copy files. I think that's fixed in later versions, but if you're accessing a w2k machine, it's tough if you can't map a network drive because of firewall restrictions.
Enter TSDropCopy:
http://www.analogx.com/contents/download/system/tsdc.htm
PuTTY is a FLOSS SSH (including SCP and SFTP) implementation for Windows, with a particularly nice Windows-compatible SSH Agent implementation. (Users moving to Linux desktops keep asking why the SSH-Agent doesn't work as nicely under X-Windows as PAgeant!)
(PuTTY even supports Win32 on Alpha.)
Re:Windows SSH
jplindstrom on 2005-07-13T20:03:44
Oh, I know about plink, pscp and all, but it doesn't fulfill the same role as SSH does on Unix; you can't remotely control a windows machine from the shell. You need a GUI to do interesting stuff on Windows. Hence TS <=> SSH.Re:Windows SSH
n1vux on 2005-07-14T18:50:50
Oh, in that sense. Yeah, TS and a few other virtualizers let you view the GUI remotely. The structure of Xwindows lets point of execution and point of display wander separately in the Unix/X universe, in ways that Windows can't.
SSH rocks because the commandline rocks.;-)
Bill
