How To Enable Telnet on Windows server 2019

Instantly Enable Telnet on Windows Server 2019: Your Quick Troubleshooting Guide

Introduction: Why Every Admin Needs Telnet

Hello, tech fans, and welcome back to Darren’s Tech Tutorials!

If you manage Windows Server environments, you know that network troubleshooting is a daily necessity. When you need to quickly check if a specific TCP port is open on a remote server—whether it’s SQL, RDP, or HTTP—there is no faster or simpler tool than Telnet.

However, if you’ve tried to use Telnet on a fresh installation of Windows Server 2019, you’ve likely run into the frustrating error: ‘telnet’ is not recognized as an internal or external command.

That’s because Microsoft does not enable the Telnet Client feature by default.

In this quick guide, we’re going to walk through the incredibly easy steps needed to enable the Telnet Client on your Windows Server 2019 machine, allowing you to instantly diagnose connectivity issues like a pro!

Why Telnet is Still Relevant (And a Quick Security Note)

Before we jump into the installation, let’s quickly address why Telnet is still valuable.

While Telnet is an old protocol and should never be used for secure, long-term remote administration (that’s what SSH and RDP are for!), it excels at one thing: being a lightweight TCP connectivity tester.

If you need to know if a firewall is blocking port 3389 to your database server, or if the web service on port 80 is listening, simply typing telnet [server IP] [port number] provides an immediate answer. It’s essential for rapid, internal network diagnostics.

Security Reminder: Since Telnet transmits data (including credentials) in plain text, only use the Telnet Client for testing purposes within a secure, controlled internal network.

Step-by-Step: Enabling the Telnet Client on Windows Server 2019

There are two primary ways to enable the Telnet Client: using the Server Manager GUI or using PowerShell. As savvy admins, we recommend the PowerShell method for speed and efficiency!

Method 1: Using PowerShell (The Quick Way)

This method requires just one command and is the fastest way to get Telnet up and running.

Open PowerShell as Administrator: Right-click the Start button and select ‘Windows PowerShell (Admin).’
Execute the Installation Command: Paste the following command and press Enter:
```
Install-WindowsFeature Telnet-Client
```
Wait for Confirmation: The installation is usually instantaneous and does not require a reboot. You will see a success message confirming the installation status is ‘Success.’

Method 2: Using the Server Manager GUI

If you prefer using the graphical interface, follow these steps:

Open Server Manager: Click the Start button, search for ‘Server Manager,’ and open it.
Start the Wizard: Click Manage in the upper right corner, and then select Add Roles and Features.
Proceed through the Wizard: Click Next on the ‘Before You Begin’ and ‘Installation Type’ screens (ensure ‘Role-based or feature-based installation’ is selected).
Select Server: Verify your server is selected under ‘Server Selection’ and click Next.
Skip Roles: Click Next immediately on the ‘Server Roles’ page, as Telnet is a ‘Feature,’ not a ‘Role.’
Select Telnet Client: On the ‘Features’ page, scroll down and place a checkmark next to Telnet Client.
Complete Installation: Click Next, then click Install. Once complete, click Close.

Testing Your New Telnet Connection

Now that the Telnet Client is enabled, it’s crucial to test it to ensure everything works as expected!

We will try to connect to a known service, like Google’s web server on port 80, just to confirm connectivity.

Open Command Prompt or PowerShell.
Run the Test Command: Use the following syntax: telnet [target address] [port number]
```
telnet google.com 80
```

Success Indicators:

If the connection succeeds: The screen will go blank, and the cursor will blink (meaning you have successfully established a TCP connection on that port). You can then press Ctrl + ] to exit the Telnet prompt, and then type quit.
If the connection fails: You will quickly receive a message stating, “Connecting To [IP Address]…Could not open connection to the host on port 80: Connect failed.” (This usually indicates a firewall is blocking the traffic or the service is down.)

Congratulations! You now have a powerful, lightweight connectivity tester right on your Windows Server 2019 machine.

Conclusion

Enabling the Telnet Client on Windows Server 2019 is a fast, straightforward process that immediately adds a powerful tool to your troubleshooting arsenal. Whether you prefer the single command in PowerShell or navigating the Server Manager GUI, you’re now equipped to quickly diagnose those frustrating network issues without relying on external tools.

If this quick guide helped you streamline your troubleshooting, please give this post a thumbs up! Don’t forget to Like and Subscribe to Darren’s Tech Tutorials for more clear, practical guides that help you master your IT environment. Let me know in the comments below what other essential features you enable immediately after spinning up a new Windows Server!

Happy troubleshooting!