Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I have a problem with ssh. When I try to login my server remotely with ssh. It will take some hold time after that time it will give me an error, connection timed out. I have checked twice with my credentials, those are correct & I try to ping to my server, I can ping it and all services are running fine in that server. But I am unable to connect.
1. do you have sshd running on the server? (ps)
2. What port is it set to service, is it listening on that port? (netstat)
3. Are you running a firewall, and is it allowing that port inbound?
4. Are there any security devices between the two machine that might block? (or NAT)
Any one of these MAY lead to the cause of the problem, but in any case must be eliminated as a factor early.
OK you checked that the server had sshd running, but the connection failing is the one FROM the server back to your workstation. Check that sshd is running on your workstation, and that any firewall you have running allow that incoming connection.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
One thing to look a is your router(s) and make sure that port 22 is enabled; for example, Linksys routers must be configured for SSHD, port 22, "both" (protocol), and checked "enabled." That stuff is in Applications and Gaming in the router.
Another is the existence of the ./.ssh directory on both ends (if you're logging in). That directory should have authorized_keys, id_rsa, id_rsa.pub and known_hosts files that were generated by ssh-keygen.
You should be able to ssh to "yourself;" log in, and enter ssh manchine_name (which should be in your ./ssh/known_hosts file).
The above sort of assumes your servers are fixed-IP and that their names, aliases and addresses are in /etc/hosts. If you're using DHCP, be sure that they're configured with IP addresses (which, basically, is fixed-IP, eh?).
show us an "netstat -an |grep LISTE" and paste us your ssh config without comments perhaps it is "cat /etc/ssh/ssh_config |grep -v "#""
Do you have SELINUX on? iptables?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.