Overview of Connection Protocols
From SecureCRT
A data path or circuit between two computers over a phone line, network cable, or other means.
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.
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.
Telephony API. A standard developed by Intel and Microsoft that manages access to phone lines on a Windows PC. This terminal emulation application uses TAPI to provide phone dialer options. TAPI compliant programs can be running at the same time, using the modem to dial out or receive calls on an "as needed" basis.
The first version of the SSH protocol which provides a way to encrypt network traffic between a client and a server.
The second version of the SSH protocol which provides a way to encrypt network traffic between a client and a server, with a slightly different set of security features than the SSH1 protocol provides.
Telnet is a protocol that provides an interface for communications between clients and servers.
Telnet over SSL (Secure Sockets Layer), a cryptographic communications protocol used to encrypt network traffic over the internet.
The process of converting a data transmission into a secret format that cannot easily be read by unauthorized individuals. See also: decryption.
SecureCRT supports the following protocols: SSH1, SSH2, Telnet/SSL, Telnet, RLogin, Serial (COM), and TAPI.
If you are using SecureCRT to connect to a BBS or any other type of terminalserver by directly dialing the remote machine using your computer's modem, you will need to use either the Serial or TAPI 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, Telnet/SSL, or RLogin protocols 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, you will need to use either the SSH1 or SSH2 protocol.
This following topics provide an explanation of the settings related to each of the protocols supported in SecureCRT:
Note: Only the protocols selected by the user during the installation process will be available.