PuTTY returns Network error: Connection timed out

I'm using an application called PuTTY to remote into a server.

I can use it from my local library and many other libraries around me (and also from Starbucks, Panera, etc.) and it works.

But I tried to use it today from my dad's house the same as before, and I get the error:

Network error: Connection timed out. 

What could be wrong?

6

4 Answers

This means PuTTY cannot make a connection to the server.

Possible causes:

• Verizon is blocking incoming or outgoing traffic/TCP connections on port 22, maybe due to the type of plan you are subscribed to or other reason.
• Your dad's router or 3G/4G hotspot is blocking incoming or outgoing traffic/TCP connections on port 22.
• You have no Internet connection and/or something has suddenly gone wrong with the TCP/IP software on your system.
• Your campus is blocking incoming or outgoing TCP connections on port 22 to/from the specific IP you are connecting from, or one of Verizon's subnets.
• You have a local firewall or antivirus software that is blocking incoming or outgoing traffic/TCP connections on port 22.
• Your PuTTY settings are incorrect.
• Your DNS isn't correctly resolving to your campus's IP address and you are actually connecting to the wrong system.

4

Simultaneous power outages at my apartment and on campus were the culprit.

2

PuTTY connects to SecureShell.

Yes, it is probably the router/Internet connection.

It is rare, but some high-class routers have the ability to drop outgoing connections.

I'm not familiar with Verizon, but it is possible they have some kind of proxy through which you connect to the Internet and this proxy doesn't allow outgoing connection.

I had similar problem at work. The work proxy was blocking port 22 (standard port for SSH). I changed it to 443 which is the HTTPS port, and it allowed me to connect to my server. To do this change, you have to modify /etc/ssh/sshd_config and change default port from 22 to 443 and then connect through that. But this requires you to connect to a server in the first place which is impossible as I see it. Or you could very quickly run to the nearest library, modify the SSH configuration file to listen to the HTTPS port instead of the standard port 22 and run back home.

But I think your best bet is to call Verizon customer support and ask them about it.

2

I was having same issue

Solution:

1) turn of Antivirus 2) Wait some time before logging in again 3-5 mins.

Done!