The original remote execution schemes were [telnet] and [rsh], but there is no reason at all for using either of those if you can possibly use [ssh] instead.

From Tcl, it's easiest to drive [ssh] as a subprocess.  To do so in general requires one of
   * [Expect] or
   * configuration of compatible keypairs, right options, ...





----
Someone frequently asks a question like, "How do use I [Tcl] to access a program on a different machine?"
(common variant:  "How do I shutdown a remote machine?")
These words turn out to cover a VERY wide territory, much of it with no particular relation to Tcl.  An answer
that satisfies the original questioner might involve:
   * [[lots of collaboration products, including Microsoft's .NET meeting, just recommended by one user]]
   * [distributed computing]
   * [Expect]
   * [psexec]
   * [rdp] [[find reference to rdp2vnc]]
   * [rtelnet], [rsh], [rexec]
   * [send]
   * [Services under Microsoft Windows NT]
   * [ssh]
   * [VNC]
   * [VPN]
   * [[Windows [telnet] server]]
   * ...

----
"[Remote file access]"