SSH Guide: Index
Both Mac clients offer intuitive interfaces; both also are well-documented. For that reason, this discussion of the Mac clients is very brief. However, for both clients, the important information is the same as for the Windows clients: the hostname and ports must be correctly specified.
Two free clients for Windows provide SSH tunneling:
As with the Mac clients, the important things to keep in mind are
the hostname and the port numbers. For both terminals, the
configuration process is straightforward. Because TTSH is an add-on to
Tera Term, it means you have to go through that one extra step before
SSH functionality is possible. [A fuller description of tunneling with
TTSH is being drafted and will be posted when finished. For now,
please see TTSH's
website.]
PuTTY, on the other hand, does not allow you to easily configure the client to handle port forwarding. As a result, it is not recommended for tunneling.
Both these clients are fairly easy to use and configure for SSH1 tunneling. The information you will need--doubtless familiar by now--is listed below. The following illustrates the procedure; we will use SecureCRT (version 3.1.2):
We discuss how to use the open-source desktop Unix emulator for Windows, Cygwin, in the section titled, Tunneling using Cygwin. Because Cygwin does emulate a Unix environment, complete with many Unix commands, those who are tunneling from a Unix-like environment (say, from a Linux machine), can refer to the discussion on Cygwin.
Back to main Help index
Necessities
Hostname: thisdomain.com
Local port: 2401
Remote port: 2401
Username: tunnel
User password: tunnel
Macintosh
Windows
SecureCRT and F-Secure SSH
Back to main Help index