PutyTa

Practical SSH guide

PuTTY Setup on Windows: Install, Configure, and Connect

PuTTY is a third-party, open-source terminal client commonly used to open SSH sessions from Windows. This guide follows the path from a verified project download to a saved connection profile and a careful first login.

On this page

Learning objectives

  • Identify what an SSH client does and where to obtain PuTTY safely.
  • Install PuTTY and configure a basic SSH session.
  • Save reusable session settings and evaluate a first-use host key prompt.
  • Recognize the most common setup errors without weakening security.

Prerequisites

  • A supported Windows computer where you may install applications.
  • A server hostname or IP address, SSH port, and username supplied by the server administrator.
  • A password or authorized private key. Never send either one through a contact form.

What PuTTY and SSH clients do

SSH (Secure Shell) is an encrypted protocol for operating a remote system over a network. An SSH client starts the connection, negotiates encryption, checks the server identity, and gives you a terminal after authentication. PuTTY provides this client functionality in a compact Windows application; it does not provide a server or an account.

PutyTa does not develop or distribute PuTTY. Obtain it only from the official PuTTY project site or its official latest-release page. Avoid advertisements or third-party pages that resemble download controls.

Install PuTTY on Windows

  1. Choose the correct package

    On the official download page, most current 64-bit Windows PCs use the 64-bit x86 MSI installer. Use an Arm installer only for Windows on Arm. If uncertain, open Settings → System → About and check “System type.”

  2. Verify the source

    Confirm the browser address is on chiark.greenend.org.uk. The project publishes checksums and signatures for users whose security process requires independent verification.

  3. Run the installer

    Open the downloaded MSI, review the publisher prompt, retain the standard components, and complete setup. Administrative approval may be required on managed computers.

  4. Open PuTTY

    Search the Windows Start menu for “PuTTY.” The initial Session panel is where connection details are entered.

Do not download an installer from PutyTa. This educational site does not host software files or present itself as an official download provider.

Configure and save a session

SessionTerminalWindowConnectionHost Name: server.example.netPort: 22Connection type: SSHSaved session: Work serverSaveOpen
Conceptual layout of the PuTTY Session panel, not a screenshot. Exact labels can vary slightly by version.

Enter the server’s DNS name, such as server.example.net, in Host Name (or IP address). Confirm the port—normally 22, but the administrator may specify another—and select SSH.

Useful settings are organized in the category tree. Under Connection → Data, an administrator may ask you to provide an auto-login username. Under Window → Appearance, adjust font size for readability. Avoid changing cryptographic algorithm preferences unless a qualified administrator has a specific compatibility requirement.

Return to Session, enter a descriptive name under Saved Sessions, and choose Save. Saved sessions store connection preferences, not your server password.

Make the first connection

  1. Load and open

    Select the saved session, choose Load, verify the hostname and port, then choose Open.

  2. Check the host key

    On first connection, PuTTY displays the server host key fingerprint. Compare it with a fingerprint obtained from the administrator through a trusted channel. Accepting it records that identity for later connections.

  3. Authenticate

    Enter the assigned username and then the password when prompted. Password characters are normally not displayed while you type. This is expected terminal behavior.

  4. Confirm the remote system

    After login, note the command prompt and any system banner. Run only commands you understand and sign out with exit when finished.

Common mistakes and quick checks

  • Wrong connection target: remove https://, URL paths, and spaces. PuTTY needs a hostname or IP address.
  • Wrong port: a web server port such as 443 is not automatically an SSH port. Use the value supplied for SSH.
  • Settings did not persist: change the options, return to Session, select the profile, and choose Save again.
  • Host key changed: do not blindly replace the saved key. A legitimate server rebuild can change it, but so can interception. Verify the new fingerprint first.
  • Login rejected: confirm the username, keyboard layout, and authentication method. Repeated guesses may trigger account protection.

For network-level errors, follow the safe SSH troubleshooting workflow. For key-based login, continue with PuTTYgen and SSH keys.

Still working through it?

Describe the step you reached and the exact error. Leave out passwords and private keys. PutyTa responds to every inquiry, but not every technical problem can be resolved.

Ask for Guidance