Results 1 to 4 of 4

Thread: Unable to connect to ssh server. But able to ping and telnet to the port 22

  1. #1

    Default Unable to connect to ssh server. But able to ping and telnet to the port 22

    Server SUSE Linux 11
    There are two servers with different networks

    1. 10.3.5.81
    2. 10.3.4.124

    # ping 10.3.4.124
    PING 10.3.4.124 (10.3.4.124) 56(84) bytes of data.
    64 bytes from 10.3.4.124: icmp_seq=1 ttl=63 time=0.380 ms

    # telnet 10.3.4.124 22
    Trying 10.3.4.124...
    Connected to 10.3.4.124.
    Escape character is '^]'.
    SSH-2.0-OpenSSH_6.6.1

    # ssh -v 10.3.4.124
    OpenSSH_6.6.1, OpenSSL 0.9.8j-fips 07 Jan 2009
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: /etc/ssh/ssh_config line 20: Applying options for *
    debug1: Connecting to 10.3.4.124 [10.3.4.124] port 22.
    debug1: Connection established.
    debug1: permanently_set_uid: 0/0
    debug1: identity file /root/.ssh/id_rsa type 1
    debug1: identity file /root/.ssh/id_rsa-cert type -1
    debug1: identity file /root/.ssh/id_dsa type -1
    debug1: identity file /root/.ssh/id_dsa-cert type -1
    debug1: identity file /root/.ssh/id_ecdsa type -1
    debug1: identity file /root/.ssh/id_ecdsa-cert type -1
    debug1: identity file /root/.ssh/id_ed25519 type -1
    debug1: identity file /root/.ssh/id_ed25519-cert type -1
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_6.6.1
    debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1
    debug1: match: OpenSSH_6.6.1 pat OpenSSH_6.6.1* compat 0x04000000
    debug1: SSH2_MSG_KEXINIT sent
    After that it hangs....
    But when i connect from outside the network to both the server using ssh i can able to connect. but its not working with each other.

    tcpdump report
    # tcpdump -i eth0 port 22 and host 10.3.4.124
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
    19:36:13.047860 IP egabhs1.64491 > egabh10ci.ssh: S 1482777917:1482777917(0) win 17920 <mss 8960,sackOK,timestamp 9525071 0,nop,wscale 7>
    19:36:13.048312 IP egabh10ci.ssh > egabhs1.64491: S 2106360063:2106360063(0) ack 1482777918 win 17896 <mss 8960,sackOK,timestamp 19123419 9525071,nop,wscale 7,nop,opt-14:03>
    19:36:13.048331 IP egabhs1.64491 > egabh10ci.ssh: . ack 1 win 140 <nop,nop,timestamp 9525071 19123419>
    19:36:13.048680 IP egabhs1.64491 > egabh10ci.ssh: P 1:24(23) ack 1 win 140 <nop,nop,timestamp 9525071 19123419>
    19:36:13.048959 IP egabh10ci.ssh > egabhs1.64491: . ack 24 win 140 <nop,nop,timestamp 19123419 9525071>
    19:36:13.060436 IP egabh10ci.ssh > egabhs1.64491: P 1:24(23) ack 24 win 140 <nop,nop,timestamp 19123420 9525071>
    19:36:13.060457 IP egabhs1.64491 > egabh10ci.ssh: . ack 24 win 140 <nop,nop,timestamp 9525072 19123420>
    19:36:13.060727 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9525072 19123420>
    19:36:13.267861 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9525093 19123420>
    19:36:13.687927 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9525135 19123420>
    19:36:14.527864 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9525219 19123420>
    19:36:16.207860 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9525387 19123420>
    19:36:19.577931 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9525724 19123420>
    19:36:26.317925 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9526398 19123420>
    19:36:39.777932 IP egabhs1.64491 > egabh10ci.ssh: P 24:1896(1872) ack 24 win 140 <nop,nop,timestamp 9527744 19123420>

    Please let me know if you need any other information."




  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,695

    Default Re: Unable to connect to ssh server. But able to ping and telnet to the port 22

    This is openSUSE forum not SUSE forum. Yes they are different

    https://forums.suse.com/forum.php

  3. #3

    Default Re: Unable to connect to ssh server. But able to ping and telnet to the port 22

    Its OpenSUSE 11.0 What we are using.

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,972

    Default Re: Unable to connect to ssh server. But able to ping and telnet to the port 22

    Quote Originally Posted by sunnysudershan View Post
    Its OpenSUSE 11.0 What we are using.
    Can you please confirm this with
    Code:
    cat /etc/SuSE-release
    Because openSUSE 11.0 is very old and most people will doubt that you are still using it.
    Henk van Velden

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •