SSH vs Telnet: A+ Network Management Guide

SSH (Secure Shell) and Telnet are both protocols used for remote CLI management, but the critical difference is encryption. Telnet transmits data in plaintext, making it vulnerable to packet sniffing, while SSH encrypts all traffic. For the CompTIA A+ exam, remember SSH uses port 22 and Telnet uses port 23.

What is the fundamental difference between SSH and Telnet?

When you're diving into the CompTIA A+ Core 1 objectives, you'll encounter several ways to manage devices remotely. At their core, both SSH (Secure Shell) and Telnet allow you to open a command-line interface (CLI) on a remote server, switch, or router as if you were sitting right in front of it. However, the way they handle your data is worlds apart.

Telnet is an old-school protocol that sends everything in plaintext. This means every keystroke, including your administrative username and password, travels across the wire in a readable format. SSH was designed specifically to replace Telnet by introducing strong encryption. When you use SSH, a secure tunnel is established, ensuring that even if someone intercepts the packets, they'll see nothing but gibberish. In a modern production environment, using Telnet for management is essentially leaving your front door wide open.

Which ports do SSH and Telnet use?

For the 220-1101 exam, memorizing port numbers is a 'low-hanging fruit' opportunity to pick up easy points. You need to know these two by heart because they frequently appear in multiple-choice questions and performance-based tasks. Telnet operates on TCP port 23, while SSH operates on TCP port 22.

Think of these ports as the specific 'doors' the network traffic uses to enter the device. If you're configuring a firewall to allow remote management, you'll likely be opening port 22 and explicitly closing port 23 to prevent unauthorized access. If you see a question asking which port should be open for 'secure remote access,' your mind should immediately jump to port 22. It's a simple distinction, but getting it wrong can cost you a point on the exam.

Why is Telnet considered a security risk in modern networks?

The danger of Telnet boils down to a technique called packet sniffing. Using a tool like Wireshark, an attacker positioned on the same network can capture the traffic flowing between your workstation and the remote device. Because Telnet lacks encryption, the attacker can simply 'follow the TCP stream' and read your login credentials in cleartext. This is a goldmine for hackers looking to escalate privileges within a network.

Beyond just credential theft, Telnet is susceptible to man-in-the-middle (MITM) attacks, where a malicious actor intercepts and potentially alters the commands you're sending to your hardware. In today's security landscape, where ransomware and advanced persistent threats are common, transmitting administrative passwords in plaintext is an unacceptable risk. This is why almost every modern enterprise has deprecated Telnet in favor of SSH.

When would you actually use Telnet today?

You might be wondering: if Telnet is so dangerous, why is it still mentioned in the A+ curriculum? The truth is, you'll still find Telnet in a few very specific, controlled scenarios. First, some legacy hardware—think of 20-year-old industrial switches or ancient mainframe systems—simply doesn't support SSH. In these cases, you might use Telnet, but only over a dedicated, isolated management VLAN that has no connection to the broader internet.

Second, network engineers often use a Telnet client as a basic troubleshooting tool to check if a specific port is open on a remote server. For example, if you want to see if a web server is responding on port 80, you can attempt to 'telnet' into that IP on port 80. While it's not used for management, it's a quick way to test connectivity before bringing in heavier diagnostic tools.

How do these protocols appear on the CompTIA A+ exam?

CompTIA loves to test your ability to apply knowledge to a scenario. You won't just be asked 'What port does SSH use?' Instead, you'll likely see a prompt like: 'A technician needs to remotely configure a core switch in a secure manner. Which of the following protocols should be used?' In this case, you'll have to choose SSH over Telnet, RDP, or FTP.

Pay close attention to keywords like 'secure,' 'encrypted,' and 'plaintext.' If the scenario mentions a security audit finding that passwords are being sent in the clear, the answer is almost certainly that the organization is using Telnet and needs to migrate to SSH. Understanding the 'why' behind the protocol choice is what separates a student who memorizes from a student who understands the material.

How can you master these network protocols for your certification?

Reading a guide is a great start, but the only way to truly lock in this knowledge is through repetitive, high-quality practice. This is where we come in. At Cert Sensei, we provide 1,000 expert-curated practice questions specifically for the CompTIA A+ Core 1 (220-1101) exam. We don't just tell you if you got the answer wrong; we provide detailed expert reasoning for every single response so you understand the logic behind the correct choice.

Our platform also features domain-level analytics, allowing you to see exactly where you're struggling. If you're consistently missing questions on network protocols like SSH and Telnet, you can use our custom quiz builder to filter for that specific domain and drill down until you've mastered it. Stop guessing and start knowing exactly where you stand before exam day.

❓ Frequently Asked Questions