Telnet on Windows: what to download and when it still makes sense
Telnet is decades old and unencrypted, yet a surprising amount of equipment on a US corporate floor still expects it: console servers, older managed switches, industrial controllers, and building systems nobody wants to touch. Windows users have two sensible ways to reach them.
Option 1 — turn on the Windows Telnet Client
- Press Start and search for Turn Windows features on or off.
- Check Telnet Client and select OK.
- Open Command Prompt and run
telnet 192.0.2.10 23.
No download is involved — the component already ships with Windows 10 and Windows 11 and simply sits disabled by default.
Option 2 — use PuTTY as your Telnet client
The same PuTTY package you install for SSH speaks Telnet. Choose Telnet as the connection type on the Session screen, set the port, and save the profile with a name. That gets you things the command-line client never had: scrollback you can search, logging to a text file, adjustable character encoding, and a saved list of every device you touch.
| Windows Telnet Client | PuTTY in Telnet mode | |
|---|---|---|
| Session logging | Manual redirection only | Built-in log file per session |
| Saved device list | None | Named session profiles |
| Also does SSH | No | Yes |
| Needs an optional feature enabled | Yes | No |
Handling Telnet responsibly
- Keep Telnet traffic on a management VLAN that never leaves the building.
- Use accounts that exist only on the device, never a shared domain credential.
- Where the hardware supports it, switch the device to SSH and retire the Telnet listener — the PuTTY SSH page covers the settings you will need.
Serial consoles: the other legacy protocol
Plenty of the same devices offer a DB-9 or USB console port. PuTTY handles that too — pick Serial, set the COM port from Device Manager, and match the speed, usually 9600 or 115200. Read how Telnet works on Windows for the protocol details behind both paths.