Overview of Connection Protocols


SecureCRT supports the following protocols: SSH1, SSH2, Telnet, serial , Local Shell, and Raw.

If you are using SecureCRT to connect [To open a Telnet or other type of communication connection between a client and a server.] to a BBS or any other type of terminal [A device usually consisting of a keyboard, a display unit such as a cathode ray tube, and a serial port used for entering and sending data to a computer and displaying any data received from the computer. Terminals are usually connected to a computer with a serial line or some other type of connection. There are many terminal types including VT100, VT102, VT220, and others.] server [A computer program that provides services to other computer programs (called clients). Often the computer on which a server program runs is also called a server. The term host is often used as a synonym for server.] by directly dialing the remote machine using your computer's modem, you will need to use the serial protocol.

If you are using SecureCRT to connect to a remote machine via the Internet or your LAN, you should use the SSH1, SSH2, Telnet protocol depending on the services provided by the remote machine to which you are connecting.

If you are using SecureCRT to establish a secure connection using encryption [The process of converting a data transmission into a secret format that cannot easily be read by unauthorized individuals. See also: decryption.] , you will need to use either the SSH1 or SSH2 protocol.

When the Raw protocol is used, little or no interpretation of the remote data takes place, which can be helpful for troubleshooting.

This following topics provide an explanation of the settings related to each of the protocols supported in SecureCRT:

Telnet Connection Settings

Serial Connection Settings

SSH1 Connection Settings

SSH2 Connection Settings

Raw Connection Settings

Note: Only the protocols selected during the installation process will be available.