PuTTY on Windows: What It Is, How It Works & Common Issues

If you manage servers, network devices, or remote Linux systems from a Windows PC, you’ve likely heard of PuTTY. It’s one of the most widely used SSH and Telnet clients on Windows, trusted by system administrators, developers, and students alike. Developed by Simon Tatham, it supports SSH, Telnet, SCP, SFTP, and serial connections with robust encryption like AES and ML-KEM. This guide explains what PuTTY is, how it works on Windows, how to use it for SSH connections, and the most common issues you may encounter, plus how to resolve them.

What Is PuTTY?

PuTTY is a free, open-source terminal emulator and network client for Windows (and other platforms), created by Simon Tatham and contributors.

It supports several network protocols, including:

• SSH (Secure Shell) – the most commonly used, secure remote login protocol.
• Telnet – legacy, unencrypted protocol (not recommended for the internet).
• Rlogin – older Unix remote login protocol.
• Raw – custom TCP connections.
• Serial – serial port connections (e.g., to routers or switches via COM ports).

On Windows, PuTTY is mainly used to open secure SSH sessions to remote Linux/Unix servers, network equipment, and sometimes Windows servers running an SSH server.

Key points:

• Free and open-source.
• Lightweight and portable (no heavy dependencies).
• Widely used in IT, DevOps, and networking.

OPERATING SYSTEM: Windows 11, Windows 10, Windows 8/8.1, Windows 7, Windows Vista, Windows XP (32-bit and 64-bit); Unix, Linux, macOS (ports)

By Simon Tatham (Free, Open-Source) | PuTTY Official Download Page

Note: Always download from www.chiark.greenend.org.uk to ensure safety. Verify GPG signatures for integrity. Portable version requires no installation.

How PuTTY Works on Windows

PuTTY provides a graphical interface to configure and open remote connections.

Connection Basics

When you start PuTTY, you’ll see the PuTTY Configuration window. Here you specify:

• Host Name (or IP address) – the server’s hostname or IP (e.g., example.com or 192.168.1.10).
• Port – usually 22 for SSH (default), or another if your server uses a custom port.
• Connection type – typically SSH.

Once configured, click Open to start a terminal session.

SSH Sessions and Authentication

After you open an SSH session:

• A terminal window appears (black background by default).
• You may see a host key prompt the first time you connect. PuTTY will ask you to confirm the server’s fingerprint—this helps prevent man-in-the-middle attacks.
• Then PuTTY prompts for a username and password, or uses public key authentication if configured.

Under the hood, PuTTY:

• Establishes an encrypted SSH connection to the server.
• Negotiates encryption and authentication methods.
• Presents an interactive shell or command-line interface.

Saving Sessions

To avoid retyping connection details every time:

1. In PuTTY Configuration, enter your host name, port, and connection type (SSH).
2. Under Saved Sessions, type a name (e.g., MyServer-Prod).
3. Click Save.

Next time you open PuTTY, just:

• Select your saved session.
• Click Load, then Open.

You can save multiple sessions for different servers (dev, staging, production, routers, etc.).

Terminal Emulation and Customization

PuTTY is a terminal emulator, meaning it displays a text-based interface from the remote system. You can customize:

• Fonts and colors (e.g., change background to dark grey, adjust text size).
• Window size and behavior.
• Keyboard mapping, bell settings, cursor style, etc.

These options are available in the Category tree on the left of the configuration window (e.g., Window, Appearance, Colours, Keyboard).

PuTTY Tools: Plink, PuTTYgen, PSCP, and PSFTP

When you install PuTTY, you also get some related tools:

• PuTTYgen – key generator for SSH key pairs (public/private keys).
• PSCP – command-line secure copy client (SCP) for transferring files.
• PSFTP – command-line SFTP client for file transfer via SSH.
• Plink – command-line interface to PuTTY’s back ends (for scripts/automation).

These tools are useful for:

• Setting up key-based authentication (PuTTYgen).
• Automating file transfers or SSH tasks from scripts (PSCP, Plink, PSFTP).

Getting Started: How to Install and Use PuTTY on Windows

Step 1: Download and Install PuTTY

1. Go to the official PuTTY site:
   https://www.chiark.greenend.org.uk/~sgtatham/putty/
   or the mirrored site https://www.putty.org/ (which redirects appropriately).

• Download the correct installer for your system:
  • 64-bit x86 for most modern Windows 10/11 PCs.
• Run the installer and follow the prompts to install PuTTY and optional tools.

Alternatively, you can download standalone executables (portable) if you don’t want a full installer.

Step 2: Make Your First SSH Connection

1. Launch PuTTY.
2. In the Session category:
   • Host Name (or IP address): enter your server’s domain or IP.
   • Port: usually 22.
   • Connection type: select SSH.
3. (Optional) In Saved Sessions, type a name and click Save.
4. Click Open.

On first connection, you’ll see a security alert:

• PuTTY will display the server’s SSH key fingerprint.
• Verify it with your server admin or hosting provider.
• If it matches, click Accept (or Yes to store it and avoid future prompts).

Then, log in with:

• login as: your SSH username.
• Enter your password when prompted (you won’t see characters as you type).

If credentials are correct, you’ll see a shell prompt (e.g., user@server:~$).

Step 3: Use PuTTY for Remote Commands

Once connected, you can:

• Run Linux commands (e.g., ls, cd, mkdir, nano, systemctl).
• Edit configuration files.
• Check logs.
• Manage services and applications.

You’re essentially operating a terminal on the remote machine while sitting at your Windows PC.

To end the session:

• Type exit or press Ctrl + D, or simply close the PuTTY window (though graceful logout is preferred).

Step 4: Using SSH Keys with PuTTY (Public Key Authentication)

For better security, you can use SSH keys instead of passwords.

Basic process:

1. Open PuTTYgen (included with PuTTY).
2. Click Generate and move your mouse to generate randomness.
3. Save the private key to your Windows PC (e.g., id_rsa.ppk).
4. Copy the public key (the text area in PuTTYgen) to your server’s ~/.ssh/authorized_keys file for your user.
5. In PuTTY’s Connection > SSH > Auth settings:
   • Click Browse… and select your .ppk private key.
6. Save these settings in your Saved Sessions and reconnect.

Now PuTTY will use your private key to authenticate, often without a password (or with a key passphrase).

Common PuTTY Issues on Windows (and How to Fix Them)

Even though PuTTY is stable and lightweight, users sometimes encounter problems. Here are some common issues and solutions.

“Network error: Connection refused”

What it means:

• Your Windows PC reached the remote host, but the target port is not open or listening.

Possible causes:

• SSH service (e.g., sshd) not running on the server.
• Wrong port number.
• Firewall or security group blocking the port.

Fixes:

• Double-check the SSH port (usually 22; some servers use custom ports).
• Ensure the SSH server is installed and running on the remote system.
• Check firewall rules on the server and any network firewalls in between.

“Network error: Connection timed out”

What it means:

• PuTTY cannot reach the server at all, or the response took too long.

Possible causes:

• Wrong IP/hostname.
• Server is offline or unreachable.
• Firewall or NAT blocking access.
• VPN or network issues on your side.

Fixes:

• Confirm the IP/hostname is correct (ping it from Windows if possible).
• Check that the server is up by connecting from another device or using a different tool.
• Verify network connectivity, VPN status, and local firewall rules.

“Server unexpectedly closed network connection”

What it means:

• The connection was established but then dropped by the server.

Possible causes:

• SSH daemon crashed or restarted.
• Incorrect login or authentication issues.
• Idle session timed out due to server-side timeout policies.
• Network instability.

Fixes:

• Try reconnecting; verify credentials.
• Check server logs (e.g., /var/log/auth.log, /var/log/secure) for clues.
• Adjust server-side SSH timeout settings if idle sessions are being closed too quickly.
• On PuTTY side, you can configure keepalives under Connection > Seconds between keepalives (e.g., 30–60 seconds) to help prevent idle timeouts.

Keyboard or Character Issues (Backspace, Arrow Keys, UTF-8)

Symptoms:

• Backspace doesn’t behave correctly.
• Arrow keys or function keys act strangely.
• Special characters (UTF-8) display incorrectly.

Fixes:

• Under Terminal > Keyboard, adjust the Backspace key setting (e.g., to Control-H) to match the remote host’s expectation.
• Under Window > Translation, set Remote character set to UTF-8 if the server uses UTF-8.
• Test different terminal options under Terminal > Features if needed.

Copy and Paste Not Working as Expected

PuTTY uses a slightly different copy/paste model than standard Windows apps:

• To copy text from PuTTY:
  • Simply select text with the mouse; it’s automatically copied to the clipboard.
• To paste into PuTTY:
  • Right-click inside the PuTTY window, or press Shift + Insert.

If it’s not working:

• Check Windows clipboard is functioning (copy/paste from another app).
• Ensure you’re not accidentally deselecting the text before you release the mouse.

“No supported authentication methods available”

What it means:

• The server is not accepting the authentication method you tried (e.g., password disabled, key required).

Fixes:

• Confirm with admin whether the server requires SSH keys only.
• If using keys, ensure PuTTY is configured with the right private key under Connection > SSH > Auth.
• Check server’s sshd_config for allowed authentication methods.

PuTTY Window Too Small or Hard to Read

If the font is tiny or the window too small:

• In Window > Appearance, adjust:
  • Font and size.
  • Bold for better readability.
• In Window, set Rows and Columns for default size.

Save these changes in your Saved Session so they apply every time.

Is PuTTY Still Needed Now That Windows Has Built-In SSH?

Windows 10 and Windows 11 include an optional OpenSSH client, which gives you a native ssh command in PowerShell or Command Prompt.

So do you still need PuTTY?

Use PuTTY if you:

• Prefer a graphical configuration UI.
• Want saved profiles with different colors, fonts, key settings, and keepalives.
• Frequently use serial connections to network devices.
• Need PuTTY’s related tools (PuTTYgen, Plink, PSCP).

Use built-in OpenSSH if you:

• Like command-line workflows and scripting.
• Work heavily with Linux/macOS and want similar ssh behavior.
• Prefer fewer third-party tools.

Many admins use both: PuTTY for ad hoc manual sessions and OpenSSH for scripts and automation.

Security Considerations When Using PuTTY

PuTTY itself is generally considered secure when obtained from the official site, but you should still follow good security practices:

1. Verify downloads
   • Download only from the official PuTTY site.
   • Check digital signatures or hashes if you’re in a high-security environment.
2. Manage host keys
   • When PuTTY warns that a server’s host key changed unexpectedly, treat it seriously—it may indicate a man-in-the-middle (MITM) attack or a server reinstallation.
3. Use SSH keys instead of passwords
   • Strong key-based authentication is generally more secure than password-only logins.
4. Avoid Telnet and insecure protocols
   • Use SSH instead of Telnet or rlogin except in specialized, isolated environments.
5. Keep PuTTY updated
   • Install newer versions when released to get security fixes and improvements.

Final Thoughts

PuTTY remains one of the most important tools for Windows users who manage remote systems. It’s:

• Lightweight and free – easy to install and use on almost any Windows PC.
• Flexible – supports SSH, Telnet, serial connections, and more.
• Powerful – with saved sessions, key-based auth, and companion tools like PuTTYgen and PSCP.

While Windows now includes a built-in SSH client, PuTTY’s graphical interface, configurability, and long history still make it a favorite for system administrators, developers, and students connecting to Linux and network devices from Windows.

Learn the basics of configuring sessions, saving profiles, and handling common connection issues, and PuTTY will become a reliable part of your Windows toolkit for secure remote access.