How to Use the telnet Command in Windows for Network Diagnostics?

Last Updated : 12 Jan, 2026

The telnet command in Windows is a lightweight, built-in tool for basic network diagnostics. It lets you test connectivity to remote hosts and verify whether specific ports are open and responding.

Although modern tools like PowerShell's Test-NetConnectionNyConnection or curl have largely superseded it, telnet remains useful for quick checks especially when those alternatives aren't available.

1. Telnet

Telnet (short for teletype network) is a client-server protocol that provides a command-line interface to remote systems over a network. It operates over TCP and defaults to port 23, but you can target any port. Key diagnostic uses include:

  • Checking if a port is open on a remote host.
  • Verifying basic TCP connectivity.
  • Interacting with text-based services (e.g., SMTP, HTTP).

Security Note: Telnet transmits data in plaintext, including credentials. Use it only for testing, never for production logins. Prefer SSH for secure remote access.

2. Enabling Telnet Client on Windows

Telnet is disabled by default on Windows 10, 11, and Server editions. Enable it via Windows Features:

  1. Press Win + R, type control, and press Enter to open Control Panel.
  2. Navigate to Programs > Programs and Features > Turn Windows features on or off.
  3. Scroll down, check Telnet Client, and click OK.
  4. Windows will install the feature (takes ~1 minute). No restart is needed.

3. Verify Installation

  1. Press Win + R, type cmd, and press Enter.
  2. Type telnet and press Enter.
  3. Success: You see the Microsoft Telnet prompt (Microsoft Telnet>). Failure: "‘telnet’ is not recognized" → re-enable the feature.

Power Tip: Use pkgmgr or PowerShell for automation:

Enable-WindowsOptionalFeature -Online -FeatureName "TelnetClient"

4. Performing Network Diagnostics with Telnet

There are several methods to identify network problems with Telnet. Here are a few such use cases:

1. Testing Open Ports: Use this command to see if a particular port is open on a remote server:

Command: telnet <hostname> <port>

For example, to test if port 80 (HTTP) is open on a server with the IP address 192.168.1.1, type:

Command: telnet 192.168.1.1 80
  • You will either see a blank screen or a response from the server if the port is open.
  • You'll get an error message saying that the connection failed if the port is closed.

2. Checking Connectivity to a Remote Server: You can use Telnet to check if a server is reachable by connecting to its default Telnet port (23):

Command: telnet <hostname>
  • If the connection is successful, it means that the server can be reached and, if Telnet is enabled on the server side, you will be able to communicate with it.
  • The server could be unavailable, offline, or the Telnet service might not be operating if the connection drops.

3. Testing SMTP Server Communication: To test connectivity with an SMTP (Simple Mail Transfer Protocol) server, utilize Telnet. This is very helpful for resolving problems with email delivery:

telnet <smtp-server> 25
  • For example, to test a connection to an SMTP server with the domain mail.example.com, type:
telnet mail.example.com 25
  • If all goes well, you will receive a welcoming message from the server and be able to communicate with it directly by sending SMTP requests.

4. Diagnosing DNS Issues: Telnet may also be used to connect to port 53 on a DNS server and confirm DNS resolution:

telnet <dns-server> 53
  • This test aids in determining whether the DNS server can be reached and is answering inquiries.

5. Practical Examples

1. Checking Web Server Availability: Use the following to see if a web server is reachable and taking connections on port 80:

telnet www.example.com 80
  • If it works, this means the web server is up and ready to receive connections, which is useful for troubleshooting website availability problems.

2. Examining Connectivity to the Remote Desktop: Port 3389 can be used to determine whether a remote desktop service is active on a server:

telnet <remote-server> 3389
  • This aids in confirming that the server can be reached and the remote desktop service is operational.

3. Confirming Email Server Setup: Test the SMTP connection to make sure an email server is configured correctly:

telnet mail.example.com 25

By using this, you may communicate with the server and make sure that demands for email delivery are being fulfilled.

6. Resolving Telnet Problems

  1. Connection rejected: The remote server's service might not be operating, or the target port might be closed, if you get a "Connection refused" notice.
  2. Unable to Connect: This error usually denotes a network problem, such as a firewall obstructing the connection or an offline distant server.
  3. Timeouts: If a Telnet command takes too long to complete, there may be a network delay or an excessive number of requests on the server.
Comment

Explore