Telnet, explained before you enable it

Telnet is a plain-text terminal protocol from an era when networks were assumed friendly. It survives on console servers and older switches, so knowing what it does and does not protect is part of the job.

What happens on the wire

The client opens TCP port 23 and both sides exchange bytes with a small negotiation for options like echo and terminal type. There is no encryption and no server authentication, so anyone on the path can read the password you type.

Enabling the Windows client

Open Turn Windows features on or off.
Check Telnet Client and confirm.
Use telnet host port from Command Prompt.

Where it still shows up

Console servers in a rack aggregating serial ports.
Older managed switches with no SSH firmware.
Industrial and building-automation controllers.
Lab equipment on an isolated segment.

Moving a device to SSH

Check for a firmware release that adds SSH, generate a host key on the device, create a local account, enable the SSH server, verify a login from PuTTY, and only then disable the Telnet listener. Keep console access available in case the change locks you out.

Questions people ask about this

Is Telnet the same as a serial console?

No, though both give you a text terminal. Telnet runs over the network; a serial console uses a physical cable and a COM port.

Why does the Telnet client seem to hang?

It usually connected but the far end is waiting for input or sending nothing. Press Enter, and use Ctrl+] to reach the client prompt.

Independent guide. Software names belong to their respective developers; always download from the vendor's own site. Back to all Windows SSH guides.