What is Telnet?
Telnet (Teletype Network) is a network protocol and a command-line tool that provides a bidirectional, interactive text-oriented communication facility using a virtual terminal connection. It was developed in 1969 and standardized by the IETF as RFC 15.
Its primary purpose is to allow a user on one computer (the Telnet client) to log in to a remote computer (the Telnet server) and execute commands as if they were sitting at the remote computer’s terminal. This makes it an essential tool for system administrators for remote management of servers, network devices (like routers and switches), and other systems.
Crucial Note on Security: Telnet transmits all data, including usernames and passwords, in plain text. This makes it extremely vulnerable to eavesdropping (packet sniffing). For this reason, it has been almost entirely replaced by the SSH (Secure Shell) protocol for any secure remote administration. Telnet is now primarily used for:
- Testing and debugging (e.g., checking if a network service port is open and responding).
- Interacting with legacy systems that do not support SSH.
- Accessing internal, air-gapped networks where security is less of a concern.
Working of Telnet (The Protocol)
Telnet operates on a client-server model.
- Connection Establishment: The Telnet client initiates a TCP connection to the Telnet server on the well-known port 23 (or another specified port).
- Negotiation (Option Handling): Once the connection is established, the client and server negotiate terminal settings and capabilities. This is done using a series of control commands. They agree on parameters like echo, line mode, and terminal type. This process ensures the server knows how to interpret the client’s keystrokes and format its output correctly.
- Terminal Interaction:
- The user types commands on the client machine.
- The Telnet client sends these keystrokes to the server.
- The Telnet server receives the characters, interprets them as commands for its operating system, and executes them.
- The output (the result of the command) is sent back from the server to the client.
- The client displays this output to the user.
- Connection Termination: The session ends when the user logs out or the connection is terminated by either end.
A key concept in Telnet is the Network Virtual Terminal (NVT). The NVT is a standardized, hypothetical device that provides a common ground for communication. Both the client and server map their native terminal characteristics to the NVT, allowing a client on one type of system (e.g., Windows) to communicate with a server on a completely different system (e.g., Linux).
Ports Used by Telnet
- Default Port: TCP Port 23. This is the standard port for Telnet server daemons to listen on for incoming connections.
- Other Ports: Telnet clients are not limited to port 23. A Telnet client can be used to connect to any TCP port. This is its most common modern use—as a simple tool to check if a service on a specific port is alive and responding. For example:
telnet google.com 80(to test a web server)telnet mail.example.com 25(to test an SMTP email server)telnet 192.168.1.1 22(to see if an SSH server is running)
Common Telnet Commands
These commands are used within the Telnet client after it has started.
| Command | Description | Example |
|---|---|---|
open | Establishes a connection to a host. | open 192.168.1.10 |
close | Closes the current connection. | close |
quit | Exits the Telnet client entirely. | quit |
status | Displays the current status of the Telnet client (connected or not, etc.). | status |
set | Sets terminal options (rarely used by average users). | set escape ^C |
unset | Unsets terminal options. | unset echo |
? or help | Displays help information for all commands or a specific command. | help open |
How to use:
- You can start the client and then use the commands:
telnet->open example.com - Or, connect directly from the command line:
telnet example.com 23
In which TCP/IP Protocol Layer does Telnet lie?
Telnet is an Application Layer protocol in the TCP/IP model.
- Application Layer: Telnet itself resides here. It defines the format of the data and the session control (like option negotiation).
- Transport Layer: It relies exclusively on TCP (Transmission Control Protocol) for reliable, connection-oriented data delivery. It does not use UDP.
- Internet Layer: Uses IP (Internet Protocol) for routing packets between the client and server.
- Network Access Layer: Uses the underlying network technology (like Ethernet or Wi-Fi).
This placement is because Telnet is a user-facing application that provides a specific service (remote terminal access) using the reliable transport services of TCP.
Which Language is Telnet Written In?
This question has two parts:
- The Telnet Protocol Specification: This is not “written” in a programming language. It is a standard, defined in documents like RFC 854 (the core NVT concept) and others. It’s a set of rules that any developer can implement.
- Telnet Implementations (Client & Server Software): The original implementations were written in C, as were the versions included with early UNIX and Linux distributions. The Telnet client found in modern Windows operating systems is also written in C/C++.
However, because the protocol is open, Telnet clients and servers can be and have been written in almost any programming language that supports network socket programming, including:
- Python (e.g., using the
telnetlibmodule) - Java
- Perl
- C++
- Go
- Ruby
For example, a system administrator might write a Python script using telnetlib to automate the process of logging into a network switch, running a command, and collecting the output.
The Motivation for Telnet’s Development
Telnet was developed in the late 1960s to solve specific problems with the computing landscape of that era. Computers then were large, expensive, and shared by multiple users, who had to access them through a physical terminal.
The Problems Telnet Addressed
There were two main issues that Telnet was designed to solve:
- Multiple Terminals per User: In organizations with several computers, a user needing to access each machine would require a separate, costly terminal for each one. This was inefficient and expensive. The text compares this to having a room full of televisions, with each one only able to show a single channel.
- Remote Access Inefficiency: To access a computer at a different physical location, a dedicated data circuit was required to connect a user’s terminal to that specific remote machine. Each circuit only allowed access to one machine, making it a very expensive and difficult process to scale.
The Telnet Solution
Telnet was created to provide a more general and flexible solution. It acted as an application protocol that ran on top of the emerging physical network and the TCP/IP protocol suite. This allowed any terminal to establish a session with any networked computer, eliminating the need for dedicated terminals and expensive, one-to-one data circuits. Essentially, Telnet enabled a user to log in and use a remote computer as if they were directly connected to it.
How Telnet Works: A Client/Server Deep Dive
Telnet’s core function is to enable a user on one machine to access and use another machine as if it were a local connection. This makes Telnet an inherently client/server protocol, a common model in many TCP/IP applications.
Client/Server Operation
- Telnet Client: This is a software program that runs on the user’s computer. It acts as an interface, processing keystrokes and commands from the user and displaying the output received from the remote machine.
- Telnet Server: This is a program running on the remote computer that has been configured to accept and manage remote sessions.
Telnet and TCP Sessions
Telnet is designed for interactive communication over a prolonged period, so it is built upon a session-based model. For this reason, it relies on the Transmission Control Protocol (TCP), which is a connection-oriented protocol.
Telnet servers “listen” for connection requests on a well-known port: TCP port number 23.
The TCP Connection Process
- When a client wants to connect to a specific server, it initiates a TCP connection.
- The server responds, and a TCP three-way handshake is performed to set up the connection.
- This TCP connection is then maintained for the entire duration of the Telnet session, which can last for hours, days, or even weeks.
- TCP’s quality of service features ensure that data is delivered reliably and in the correct order, and that the data transfer rate is managed appropriately for both the client and the server.
A Telnet server can support many simultaneous sessions from different users. It keeps each session distinct by identifying it using the client’s IP address and port number.
Data Flow and Session Interaction
Since TCP is a full-duplex protocol, both the client and the server can send information to each other at any time during the Telnet session.
- By default, both devices start by using the standard Telnet Network Virtual Terminal (NVT) method for encoding data and commands.
- They can also negotiate the use of Telnet options to add more functionality to the session. This negotiation typically happens in a “burst” at the beginning of a session and less frequently thereafter.
With the TCP connection established, the Telnet client and server act as a bridge between the user and the remote host. To the user, the Telnet session feels identical to sitting at a terminal directly connected to the remote machine. The session usually begins with the server sending a login prompt asking for a username and password. Once the user provides valid information, they are logged in and can use the host according to their account’s permissions.
Beyond Remote Login
While Telnet is most commonly associated with remote login, its protocol is flexible enough for a variety of functions. The administrator of the computer running the Telnet server decides how it will be used.
For example, a Telnet server can be directly interfaced with a program or service. The article recalls a public Internet server that provided weather information via Telnet. Instead of a login prompt, users would see a menu of weather options.
Key Takeaway: Telnet is a client/server protocol that uses TCP to create a reliable session between a user terminal and a remote host. The client handles user input, while the server manages the connection to the host. While often used for remote logins, the protocol’s design is versatile and can be used for various other purposes.
Summary of Key Points
| Aspect | Detail |
|---|---|
| Full Name | Teletype Network |
| Purpose | Remote terminal access and command execution |
| Key Feature | Text-based, bidirectional communication |
| Key Weakness | No encryption (all data is sent in plain text) |
| Default Port | TCP 23 |
| Underlying Transport | TCP (Reliable, connection-oriented) |
| TCP/IP Layer | Application Layer |
| Architecture | Client-Server |
| Common Use Today | Testing open ports and debugging network services |
| Secure Alternative | SSH (Secure Shell) |
| Implementation Language | Primarily C, but possible in any language (Python, Java, etc.) |
Understanding the Telnet Command Structure
The basic syntax is:
telnet [OPTIONS] [HOST [PORT]][OPTIONS]: These are the flags like-l,-d,-4, etc., that change the behavior of the Telnet client.[HOST]: This is the address of the remote machine you want to connect to. It can be an IP address (e.g.,192.168.1.1) or a domain name (e.g.,google.com).[PORT]: This is the TCP port number on the remote host you want to connect to. If you omit this, it defaults to the standard Telnet port, 23.
General Options (With Examples)
1. -4 / -6: Force IP Version
-4: Forces Telnet to use only IPv4 addresses.-6: Forces Telnet to use only IPv6 addresses.
Example:
telnet -4 google.com 80Explanation: This command tries to connect to google.com on port 80 (HTTP) but will only use an IPv4 address for the connection, even if an IPv6 address is available.
2. -a / -l: Automatic Login
-a: Attempts automatic login using your current username on the local machine.-l USER: Attempts automatic login using the specifiedUSERname.
Example:
telnet -l myusername 192.168.1.15Explanation: This command connects to the Telnet server at 192.168.1.15 on port 23 and automatically sends the username myusername to the remote host. You will still likely be prompted for a password. This is highly insecure as the password is still sent in plain text.
3. -d: Debug Mode
-d: Turns on socket-level debugging. This shows the raw TCP communication details under the hood, which is invaluable for troubleshooting why a connection might be failing.
Example:
telnet -d example.com 25Output & Explanation:
telnet: Trying 93.184.216.34...
telnet: Trying 2606:2800:220:1:248:1893:25c8:1946...
telnet: Connected to example.com.
telnet: Escape character is '^]'.This shows you the exact IP addresses (both IPv4 and IPv6) that Telnet is trying to connect to, and confirms when the connection is established.
4. -e: Set Escape Character
-e CHAR: Changes the escape character from the defaultCtrl+]to another character (CHAR). The escape character is used to drop into Telnet command mode from a live session.
Example:
telnet -e ^# 192.168.1.1Explanation: This connects to 192.168.1.1. During the session, instead of pressing Ctrl+] to get the telnet> prompt, you would press Ctrl+#. The ^ symbol represents the Ctrl key.
5. -E / -8 / -L: Data and Escape Control
-E: Disables the escape character entirely. You cannot interrupt the session to use Telnet commands.-8: Requests an 8-bit data path instead of the default 7-bit. This is for older systems that needed full 8-bit support for extended character sets.-L: Specifies an 8-bit data path on output only.
Example:
telnet -E 192.168.1.1Explanation: Connects to the device, and you are “stuck” in the session until the remote server disconnects or you close your terminal window, as you can’t use Ctrl+] to escape.
6. -n: Trace to File
-n FILE: Records the entire trace of the connection (all the raw data sent and received) into the specifiedFILE.
Example:
telnet -n trace.log google.com 80Explanation: After running this, the file trace.log will contain a complete log of every byte transmitted during the Telnet session to Google’s web server. This is a powerful tool for protocol analysis.
7. -r: Rlogin Mode
-r: Uses a user-interface similar torlogin. This provides a more streamlined experience if the remote server is also running anrlogindaemon, mimicking its behavior (like having a~as an escape character).
Encryption and Authentication Options (-x, -k, -X)
These options are largely obsolete and ineffective. They were attempts to add security to Telnet but were never widely adopted or standardized. The encryption was weak and vulnerable. The industry-standard solution was to abandon Telnet entirely in favor of SSH, which was built with strong encryption from the ground up.
-x: “Encrypt” the data stream, if possible. In practice, it almost never is.-k REALM/-X ATYPE: Related to the obsolete Kerberos authentication system for Telnet.
You should never rely on these options for security. Use SSH instead.
Most Common Modern Use: Testing Network Services
The most practical use for telnet today is as a simple network diagnostic tool to check if a TCP port is open and if a service is responding.
Live Example 1: Testing a Web Server (HTTP)
telnet google.com 80What happens:
- The Telnet client establishes a TCP connection to
google.comon port 80. - If the connection is successful, you get a blank screen with a cursor. This means the port is open and a service (likely an HTTP server) is listening.
- You can now type an HTTP command. Since it’s a text-based protocol, this works.
http GET / HTTP/1.1 Host: google.com (Press Enter twice) - The web server will respond by dumping the raw HTTP headers and the HTML content of Google’s homepage directly into your Telnet window! This proves the connection is fully functional.
Live Example 2: Testing an Email Server (SMTP)
telnet mx.example.com 25What happens:
- Connects to the mail server on port 25.
- If successful, the SMTP server will send a welcome banner, e.g.,
220 mail.example.com ESMTP Postfix. - You can then interact with it using SMTP commands:
smtp EHLO test.com MAIL FROM: <test@test.com> RCPT TO: <user@example.com> DATA This is a test email from telnet. . QUIT
This allows you to test and debug the mail server manually.
Live Example 3: Checking if a Port is Open
telnet 192.168.1.10 22- If you see:
SSH-2.0-OpenSSH_8.9p1→ The port is open, and an SSH server is running. - If you see:
Connecting To 192.168.1.10...Could not open connection to the host, on port 22: Connect failed→ The port is closed, blocked by a firewall, or no service is running.
Summary
While its original purpose (remote login) is now obsolete due to security concerns, the Telnet client remains a valuable tool in a network administrator’s or developer’s toolkit precisely because it’s a “dumb” raw TCP client. Its ability to connect to any port and send/receive plain text makes it perfect for quick service checks and protocol debugging. The options in the help menu (-d, -n, -e) give you fine-grained control over how you conduct these tests.
