• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 752
  • Last Modified:

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

Hi,

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.

oracle@node2:
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
oracle@node2:

Thanks
Investo
0
Investo
Asked:
Investo
1 Solution
 
woolmilkporcCommented:
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.
0
 
InvestoAuthor Commented:
on node1 i see it running

11:49:40 # service sshd status
openssh-daemon (pid  42338) is running...
0
 
woolmilkporcCommented:
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?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Matt VCommented:
Also make sure the local firewall on node1 is allowing SSH in. (iptables)
0
 
1ly4meCommented:
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.
0
 
InvestoAuthor Commented:
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.

Thanks
Investo
0
 
InvestoAuthor Commented:
The issue was fixed by my network team. Sorry i dont have any details of the solution
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now