How to Enable and Use Telnet in Windows CMD (2026 Guide)

Telnet is a network protocol that lets you connect to remote computers and devices through the command line. If you need to troubleshoot network issues, test ports, or access remote servers, understanding telnet in Windows CMD will save you time and frustration.

This guide shows you exactly how to enable, use, and troubleshoot telnet through the Windows command prompt, with real examples you can follow right now.

What Is Telnet CMD and Why Use It?

Telnet CMD refers to using the telnet command in Windows Command Prompt to establish text-based connections to remote hosts. Originally designed for remote computer access, telnet is now primarily used for:

• Testing if specific network ports are open and accepting connections
• Troubleshooting mail servers, web servers, and other network services
• Checking connectivity to devices like routers and switches
• Learning how network protocols work at a fundamental level

Important security note: Telnet sends data in plain text without encryption. Never use it for transmitting passwords or sensitive information over public networks. For secure remote access, use SSH instead.

How to Enable Telnet in Windows

Windows doesn’t enable telnet by default. Here’s how to turn it on:

Method 1: Enable Through Control Panel

1. Open Control Panel
2. Click “Programs”
3. Click “Programs and Features”
4. Click “Turn Windows features on or off” in the left sidebar
5. Scroll down and check the box next to “Telnet Client”
6. Click “OK”
7. Wait for Windows to install the feature
8. Click “Close” when finished

Method 2: Enable Through Command Prompt (Admin)

1. Right-click the Start button
2. Select “Windows Terminal (Admin)” or “Command Prompt (Admin)”
3. Type this command:

dism /online /Enable-Feature /FeatureName:TelnetClient

4. Press Enter
5. Wait for the success message

The command prompt method works faster and doesn’t require navigating through menus.

Basic Telnet CMD Syntax and Commands

Opening a Telnet Connection

The basic syntax is:

telnet [hostname or IP] [port]

Example:

telnet google.com 80

This connects to Google’s web server on port 80.

Common Telnet Commands

Once connected to a telnet session, these commands control your connection:

Command	Function
open hostname port	Open a connection to a host
close	Close the current connection
quit	Exit telnet
set	Configure telnet options
status	Show current connection status
? or help	Display available commands

To access the telnet command prompt while connected, press Ctrl + ]. This brings up the “Microsoft Telnet>” prompt where you can type commands.

Practical Examples: Testing Network Connectivity

Test if a Web Server Is Running

telnet example.com 80

If the connection succeeds, you’ll see a blank screen. The connection is working.

If it fails, you’ll see “Could not open connection to the host.” The port is blocked or the service isn’t running.

Test SMTP Email Server

telnet mail.example.com 25

A successful connection shows something like:

220 mail.example.com ESMTP Postfix

This confirms the mail server is accepting connections on port 25.

Test SSH Availability

telnet server.example.com 22

You should see:

SSH-2.0-OpenSSH_8.2p1

This means SSH is running and accessible.

Test Custom Application Ports

telnet 192.168.1.100 8080

Replace the IP and port with your application’s details. This helps diagnose if your custom application is listening on the correct port.

Step-by-Step: Troubleshooting with Telnet

Diagnosing Port Issues

Problem: Your application can’t connect to a remote service.

Solution steps:

1. Open Command Prompt
2. Type telnet [server-address] [port-number]
3. Observe the result

If connection succeeds: The port is open. Your application issue is likely with authentication or application-level protocols.

If connection fails: The port is blocked by a firewall, the service isn’t running, or the server is unreachable.

Testing Firewall Rules

After configuring firewall rules, use telnet to verify they work:

telnet internal-server.local 3389

This tests if Remote Desktop Protocol (port 3389) is accessible through your firewall.

Checking Web Server Response

1. Connect to the web server:

telnet yourwebsite.com 80

2. Type this HTTP request (press Enter twice after the last line):

GET / HTTP/1.1
Host: yourwebsite.com

3. You’ll see the HTTP response headers and HTML content

This shows exactly what the web server returns, helpful for debugging HTTP issues.

Common Telnet Errors and Fixes

“Telnet is not recognized as an internal or external command”

Cause: Telnet client isn’t installed.

Fix: Follow the enable instructions in the section above.

“Could not open connection to the host, on port XX: Connect failed”

Causes and fixes:

• Wrong IP or hostname: Verify the address with ping [hostname]
• Firewall blocking: Check Windows Firewall and network firewall settings
• Service not running: Confirm the remote service is active
• Wrong port number: Double-check the port number for your service

Connection Immediately Closes

Cause: The service rejected your connection or requires authentication.

Fix: Some services like SSH will close telnet connections because they expect encrypted communication. This is normal behavior.

“Press any key to continue” or Hanging Connection

Cause: The connection succeeded but the service is waiting for input.

Fix: This actually means success. The port is open and listening. Press Ctrl + ] then type quit to exit.

Telnet Alternatives for Modern Networks

While telnet remains useful for testing, these alternatives offer better security and features:

PuTTY

A free terminal emulator supporting telnet, SSH, and other protocols. Download from PuTTY’s official site for a graphical interface with more features than CMD telnet.

PowerShell Test-NetConnection

Windows PowerShell includes built-in connectivity testing:

Test-NetConnection -ComputerName google.com -Port 80

This provides detailed output without enabling telnet.

Nmap

For comprehensive port scanning and network discovery, Nmap offers advanced capabilities beyond simple telnet testing.

Advanced Telnet Usage

Specify Local Port

You can specify which local port to use:

telnet -a [source-port] [hostname] [destination-port]

This helps when testing source-based firewall rules.

Using Telnet in Scripts

Create batch files for repeated testing:

@echo off
echo Testing web server...
telnet webserver.local 80
echo Testing mail server...
telnet mailserver.local 25
pause

Save as network-test.bat and run when needed.

Telnet Configuration File

Advanced users can create custom telnet configurations, though this rarely applies to basic CMD usage.

Security Considerations

Never Use Telnet for Sensitive Data

Telnet transmits everything in plain text. Anyone with network access can read:

• Usernames and passwords
• Email content
• File contents
• Commands you execute

When Telnet Is Acceptable

Safe telnet use cases:

• Testing connectivity on isolated networks
• Troubleshooting during initial server setup
• Learning network protocols in lab environments
• Quick port checks where no data is transmitted

Secure Alternatives

For actual remote management:

• SSH (Secure Shell): Encrypted remote access
• HTTPS: Secure web communication
• SFTP: Secure file transfer
• VPN: Encrypted network tunneling

Telnet vs SSH: Key Differences

Feature	Telnet	SSH
Encryption	None	Full encryption
Default Port	23	22
Authentication	Plain text	Encrypted
Data Transfer	Unencrypted	Encrypted
Modern Use	Port testing	Remote management
Security	Vulnerable	Secure

Frequently Asked Questions

How do I exit a telnet session in CMD?

Press Ctrl + ] to enter command mode, then type quit and press Enter. Alternatively, press Ctrl + C to force close the connection. If the window is completely frozen, close the Command Prompt window entirely.

Why does telnet fail when SSH works fine?

SSH and telnet use different ports (SSH uses 22, telnet uses 23 by default). When you specify a port like telnet server.com 22, telnet connects to that port but can’t complete the SSH handshake because telnet doesn’t speak the SSH protocol. The connection attempt proves the port is open, which is useful for testing.

Can I use telnet to check if a website is down?

Yes. Use telnet website.com 80 for HTTP or telnet website.com 443 for HTTPS. If the connection succeeds, the web server is running. If it fails, the server is down, blocked, or the domain doesn’t resolve. Combine with ping website.com to determine if it’s a server issue or network issue.

Is telnet available on Windows 11?

Yes. Windows 11 includes the telnet client, but you must enable it manually using the same methods described for Windows 10. Microsoft keeps this feature available for legacy support and network troubleshooting purposes.

What ports should I test with telnet for common services?

Common ports include: HTTP (80), HTTPS (443), SMTP (25), POP3 (110), IMAP (143), FTP (21), SSH (22), RDP (3389), MySQL (3306), PostgreSQL (5432), and DNS (53). Always verify the specific port your service uses, as administrators often configure non-standard ports for security.

Summary

Telnet in Windows Command Prompt remains a valuable troubleshooting tool in 2026. While outdated for secure communications, it excels at quick port testing and network diagnostics.

Key takeaways:

• Enable telnet through Windows Features or DISM command
• Use syntax: telnet [host] [port] for basic connectivity testing
• Never transmit sensitive data over telnet
• Telnet proves if ports are open and services are listening
• Modern alternatives like SSH and PowerShell offer better security

Quick reference for immediate use:

1. Enable telnet: dism /online /Enable-Feature /FeatureName:TelnetClient
2. Test connection: telnet [hostname] [port]
3. Exit connection: Press Ctrl + ] then type quit

Keep telnet in your troubleshooting toolkit for those moments when you need fast, simple connectivity verification. For everything else, especially remote management and data transfer, use encrypted alternatives like SSH.

Understanding telnet CMD fundamentals gives you deeper insight into how network communications work, making you more effective at diagnosing and solving connectivity problems across your entire network infrastructure.