Connect to Debian from Win with ssh/putty - Error: "connection timed out"
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
To check the firewall, can you run the command iptables -S INPUT on the Linux system? You need to be root to do that.
I just saw that you have a public IP address. I can ping 95.170.82.133 as well, and I can also connect to it with ssh. The problem must be your putty configuration.
Code:
[root@athlon64 pam_unix]# ping 95.170.82.133
PING 95.170.82.133 (95.170.82.133) 56(84) bytes of data.
64 bytes from 95.170.82.133: icmp_seq=1 ttl=49 time=288 ms
64 bytes from 95.170.82.133: icmp_seq=2 ttl=49 time=283 ms
^C
--- 95.170.82.133 ping statistics ---
3 packets transmitted, 2 received, 33% packet loss, time 2216ms
rtt min/avg/max/mdev = 283.666/286.327/288.989/2.714 ms
[root@athlon64 pam_unix]# ssh 95.170.82.133
The authenticity of host '95.170.82.133 (95.170.82.133)' can't be established.
RSA key fingerprint is 23:d6:f7:c3:54:68:60:e2:e7:41:f2:16:7a:3e:e1:24.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '95.170.82.133' (RSA) to the list of known hosts.
root@95.170.82.133's password:
root@95-170-82-133:/home/emanuel# iptables -S INPUT
-P INPUT DROP
-A INPUT -j ufw-before-logging-input
-A INPUT -j ufw-before-input
-A INPUT -j ufw-after-input
-A INPUT -j ufw-after-logging-input
-A INPUT -j ufw-reject-input
-A INPUT -j ufw-track-input
root@95-170-82-133:/home/emanuel#
I just saw that you have a public IP address. I can ping 95.170.82.133 as well, and I can also connect to it with ssh. The problem must be your putty configuration.
Mumble, with the same conf I can access via Putty to many other server, but from 3 day ago I can't connect to 95.170.82.133. I don't understand why!
Mumble, with the same conf I can access via Putty to many other server, but from 3 day ago I can't connect to 95.170.82.133. I don't understand why!
I can see that the Ubuntu firewall does things quite differently than my Centos firewall
Still, the fact is that I can connect to your system from thousands of kilometers away (if it is in Italy). Unfortunately I don't know enough about putty to help you.
You could find other SSH applications that run on Windows and test with them. Or boot your PC with a Linux LiveCD and see what happens. As I lean more towards UNIX, I use Cygwin and OpenSSH on my Windows PC.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.