SSH error - connect to address node1 port 22: Connection timed out

Posted on 2012-09-18
Last Modified: 2012-10-02

I am able to ssh from node1 to node2, but not from node2 to node1

when i ping node2 from node1 i see a nat ip for node2. Node2 is at client hosted and node1 is in datacenter. Network team says SSH access (TCP/22) is already open between these two ACL.

how do i troubleshoot this issue, any clue please.

10:31:40 $ ssh -vv node1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to node1 [node1] port 22.
debug1: connect to address node1 port 22: Connection timed out
ssh: connect to host node1 port 22: Connection timed out

Question by:Investo
    LVL 68

    Expert Comment

    node1 does not run an sshd server process.

    Is sshd installed on node1?

    The client interface "ssh" and the server component "sshd" are independent of each other (in a way), so the fact that you can run "ssh" on node1 does not necessarily mean that there is also "sshd" installed.

    Author Comment

    on node1 i see it running

    11:49:40 # service sshd status
    openssh-daemon (pid  42338) is running...
    LVL 68

    Expert Comment

    What do you see on node1 with

    telnet localhost 22


    If you see the OpenSSH banner then the local ssh server is indeed functional
    and you should ask your network admins one more time if there isn't  yet some kind of network component (a firewall?) between the nodes inhibiting access to port 22 on node1 from node2.

    If you don't see the banner restart the sshd service and retry.

    If it still doesn't work check on node1 if there is an /etc/hosts.deny file.

    Also examine /etc/ssh/sshd_config on node1. Do you see any directives which might be responsible for your issue?
    LVL 22

    Expert Comment

    by:Matt V
    Also make sure the local firewall on node1 is allowing SSH in. (iptables)
    LVL 5

    Expert Comment

    Do a nmap from node2 and see port 22 is open or not.
    node2# nmap node1

    This will list all the open ports for node1.

    Accepted Solution

    My network team fixed the issue saying they missed "someting from their end" when i asked wat that something was, no response :(:(:(

    Anyways thanks a lot guys for taking your time to respond to my question.


    Author Closing Comment

    The issue was fixed by my network team. Sorry i dont have any details of the solution

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Setting up Secure Ubuntu server on VMware 1.      Insert the Ubuntu Server distribution CD or attach the ISO of the CD which is in the “Datastore”. Note that it is important to install the x64 edition on servers, not the X86 editions. 2.      Power on th…
    Linux users are sometimes dumbfounded by the severe lack of documentation on a topic. Sometimes, the documentation is copious, but other times, you end up with some obscure "it varies depending on your distribution" over and over when searching for …
    Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
    Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

    732 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now