hey guys,
i have a ssh problem i would like u to help me on.
lets assume im on node1 when i type the command
ssh node2@ip
the terminal hangs up a bit then an error message stating
that connection timeout
but here is a thing:
i cant ping to node2
but i can terminate the ping manually using ctrl+c
when i terminate the ping usual message appears stating
10 packets transmitted, 100% loss
ps: when i go to node3 and ssh to node2 it works fine and also i can ping from node3 to node2 very fine.
and the firewalls are down at all nodes
when i typed the command ssh -vvv node3@ip from node1 it gave me
debug1:Reading configuration data /etc/ssh/ssh_config
debug1:Applying options for *
debug2:ssh_connect: needpriv 0
debug1:connecting to node3 [10.43.42.1] port 22
debug1:connect to address 10.43.42.1 port 22: connection timed out
ssh:connect to host node3 port 22: connection timed out
and vice versa when i was on node3 and tried to ssh -vvv node1@ip
debug1:Reading configuration data /etc/ssh/ssh_config
debug1:Applying options for *
debug2:ssh_connect: needpriv 0
debug1:connecting to node3 [10.43.42.2] port 22
debug1:connect to address 10.43.42.2 port 22: Network is unreachable
ssh:connect to host node3 port 22: Network is unreachable
“network is unreachable” usually means that the problem is local, not the remote machine. When you ran that test, the local machine is either blocking or can’t properly resolve the remote machine.
There are other reasons besides a firewall which can cause network transmission failure…
The Service (SSH in this case) could be disabled or down.
If you’re crossing network devices, those devices could be filtering or blocking traffic
The port could be already in service connecting to a different machine (busy).
You could have degraded network links resulting in packet loss even to the point you can’t complete a 3-way handshake.
Discovery and Resolution could be wrong. Clear caches and initiate re-discovery.
Authentication Provider could be down.
Of course, the ideal connection is a direct PC to PC link only a few feet long which would avoid many possible network related issues.
On 02/21/2011 11:06 PM, suseTOMA wrote:
>
> any one plz help me on that
have you setup “node2” with a functioning sshd and configured it to
expect and accept a knock on the door from “node1”?
see man ssh
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
> but here is a thing:
> i cant ping to node2
> but i can terminate the ping manually using ctrl+c
> when i terminate the ping usual message appears stating
> 10 packets transmitted, 100% loss
You have a network problem, ssh is irrelevant.
> ps: when i go to node3 and ssh to node2 it works fine and also i can
> ping from node3 to node2 very fine.
> and the firewalls are down at all nodes
Routing problem, then.
Post your routes on both computers.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
