Fixing PuTTY Network Error: Connection Refused and Connection Timed Out (Troubleshooting Guide)

You open PuTTY, enter your server IP, click Open, and suddenly you’re greeted with a PuTTY network error.

Either:

Network error: Connection refused
Network error: Connection timed out

If you manage servers, work with VPS hosting, or just connect to a Linux machine regularly, this situation is frustrating and disruptive. The problem feels technical, but in most cases, the fix is straightforward once you understand what the error really means.

In this guide, we’ll walk you through exactly how to troubleshoot and fix both errors step by step so you can get back into your server quickly.

Understanding the Difference Between the Errors

Before jumping into commands and firewall rules, it’s important to understand what these two errors are actually telling you.

What “Connection Refused” Means?

When you see:

Network error: Connection refused

It usually means:

Your computer successfully reached the server
The server rejected the connection on that port

This often happens when:

SSH is not running
The SSH port is closed
A firewall is blocking the port

This error appears almost instantly because the server responds right away with a rejection.

What “Connection Timed Out” Means?

When you see:

Network error: Connection timed out

This is different.

It usually means:

Your computer cannot reach the server at all
Traffic is being blocked somewhere
The server might be offline

This error takes longer because your system waits for a response that never comes.

Understanding this difference is critical when troubleshooting a PuTTY network error, because each one points to a different root cause.

Initial Checks Before Going Further

Before editing config files or rebooting servers, verify these basics:

Double check the IP address
Confirm the correct port number, default is 22
Ensure SSH is selected in PuTTY
Try pinging the server
Try connecting from a different network if possible

Small mistakes cause a surprising number of connection issues.

Fixing “PuTTY Connection Refused”

Let’s start with the more common scenario.

1. Check if SSH is Running

If SSH is not running on your Linux server, PuTTY will immediately refuse the connection.

On the server, run:

sudo systemctl status ssh

If it is inactive, start it:

sudo systemctl start ssh

Then try connecting again.

If SSH was stopped, that alone explains the PuTTY network error.

2. Confirm SSH is Listening on the Correct Port

Sometimes SSH is running but on a different port.

Check with:

sudo ss -tulnp | grep ssh

Look for something like:

LISTEN 0 128 0.0.0.0:22

If you see another port number, update PuTTY to use that port instead of 22.

3. Check the Server Firewall

A firewall blocking port 22 can trigger connection refused.

When working with UFW (Uncomplicated Firewall):

sudo ufw status

If port 22 is not allowed:

sudo ufw allow 22

If you are using a cloud provider like DigitalOcean, Amazon Web Services, or Google Cloud, also check the cloud firewall or security group settings.

Make sure inbound traffic on port 22 is allowed.

4. Verify SSH Configuration

Open the SSH config file:

sudo nano /etc/ssh/sshd_config

Check:

Port number
ListenAddress
PermitRootLogin settings

After making changes:

sudo systemctl restart ssh

Misconfigured SSH settings are a frequent cause of PuTTY network error messages.

Fixing “PuTTY Connection Timed Out”

Now let’s handle the more serious sounding error.

1. Check if the Server is Online

If the server is powered off or crashed, you will get a timeout.

Check your hosting dashboard
Try rebooting from the provider panel
Confirm the IP address is still assigned

No server response means PuTTY cannot connect at all.

2. Test if Port 22 is Reachable

On Windows PowerShell:

Test-NetConnection yourserverIP -Port 22

If it shows the port is not reachable, traffic is blocked somewhere.

This helps confirm whether the PuTTY network error is network related or server related.

3. Check Local Firewall or Antivirus

Sometimes the issue is not on the server side.

Disable Windows Defender Firewall temporarily for testing
Check third party antivirus firewall rules
Try a different network

Corporate networks and some ISPs block outbound SSH connections.

4. Verify Port Forwarding for Home Servers

If your server is hosted at home:

Log into your router
Forward port 22 to the internal IP of your Linux machine
Confirm the internal IP has not changed

Without proper port forwarding, timeouts are guaranteed.

5. Check for IP Bans

Security tools like Fail2Ban or CSF can temporarily block your IP after failed login attempts.

If you suspect a ban:

Access the server via hosting console
Remove your IP from the ban list
Restart the firewall service

IP blocking is a common hidden cause of PuTTY network error problems.

Quick Cause Reference Table

Use this as a fast diagnostic guide when troubleshooting.

Issue	Connection Refused	Connection Timed Out
SSH not running	Yes	No
Firewall blocking	Yes	Yes
Server offline	No	Yes
Wrong port	Yes	Yes
ISP blocking	No	Yes

How to Prevent Future PuTTY Connection Errors?

Once everything works again, take steps to reduce future issues:

Keep SSH enabled on boot
Document any custom SSH ports
Allow your IP in firewall rules
Use SSH key authentication
Monitor server uptime

Being proactive reduces emergency troubleshooting later.

Wrapping Up

A PuTTY network error can look intimidating at first, especially when you are locked out of a production server. In reality, most cases fall into a few predictable categories such as SSH not running, firewall blocks, wrong port configuration, or the server being offline.

Approach it methodically. Determine whether it is a connection refused or connection timed out situation, then follow the appropriate troubleshooting path.

Once you understand how these errors behave, fixing a PuTTY network error becomes less of a crisis and more of a routine maintenance task.

If you regularly manage servers, bookmarking this guide will save you time the next time PuTTY decides not to cooperate.

What’s your go-to PuTTY trick? Leave your thoughts in the comments below. If this post was useful, you might want to check our blog on encrypting PuTTY session logs.