Telnet is a set of components that provide terminal-like access to a remote computer. A Telnet session requires a Telnet client that will serve as the remote terminal and a Telnet server, which receives the connection request and allows the connection. This relationship is depicted in Figure 15.1.
Telnet is also a protocol—a system of rules defining the interactions between Telnet servers and clients. The Telnet protocol is defined in a series of RFCs. Because Telnet is based on a well-defined open protocol, it can be and has been implemented on a wide range of hardware and software systems. The basic purpose of Telnet is to provide a means by which keyboard commands typed by a remote user can cross the network and become input for a different computer. Screen output related to the session then crosses the network from that different computer (the server) to the client system (see Figure 15.2). The effect is that the remote user can interact with the server as if he were logged in locally.
where hostname is the name of the computer to which you'd like to connect. (You can also enter an IP address instead of a hostname.) The preceding command launches the Telnet application. When Telnet is running, the commands you enter are executed on the remote computer. Telnet also provides some special commands that you can use during a Telnet session, as follows:
On graphics-based platforms such as Microsoft Windows, a Telnet application might have its own icon and run in a window, but the underlying commands and processes are the same as with a text-based system. Consult your vendor documentation.
Telnet is an extremely useful and important tool on internal Unix networks. A system administrator can use Telnet to perform routine administration on remote computers. An admin can work from a single desktop computer and access a server across the network to restart a process, delete a file, create a new directory, or check system statistics. The recent emphasis on security has placed some restrictions on the free use of Telnet. The problem is that Telnet gives network intruders what they want more than anything—direct access to a terminal session on a remote server. The Telnet standard supports password authentication, but passwords typically are transported as clear text. You almost never see Telnet deployed on the open Internet and, on internal networks where security is important, Telnet is usually deployed with some restrictions on who uses it and what they can do with it.
By the Way
The emergence of Virtual Private Networks provides new opportunities for using Telnet in situations that once would have been considered insecure. See Hour 20, "TCP/IP Security," for more on VPNs.