Find the answer to your Linux question:
Results 1 to 7 of 7
I have a CentOS server (2.6.9-55.0.12.plus.c4smp #1 SMP Fri Nov 2 11:32:03 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux) with OpenSSH_3.9p1, OpenSSL 0.9.7a. I have all routers, firewalls, etc... setup correctly ...
  1. #1
    Just Joined! Loy Glenn's Avatar
    Join Date
    Sep 2008
    Location
    Houston,TX
    Posts
    89

    [SOLVED] SSH Client not connecting

    I have a CentOS server (2.6.9-55.0.12.plus.c4smp #1 SMP Fri Nov 2 11:32:03 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux) with OpenSSH_3.9p1, OpenSSL 0.9.7a.
    I have all routers, firewalls, etc... setup correctly (well, I think so, but I have this 1 problem)
    From the CentOS server I can ssh to myself (using both loopback and LAN ip addresses)
    I can SSH into the CentOS server from abroad (LAN and WAN)
    IPTABLES has been set to ALLOW everything as well as having been shut down.
    I cannot ssh out as a client from the CentOS server to anywhere (except the server itself).
    I am trying to connect via ssh to ssh servers which do work.
    Here is the output from attempting to connect to my computer from the server (LAN connection)

    root@/ 2# ssh -vv loy@192.168.1.105
    OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to 192.168.1.105 [192.168.1.105] port 22.
    debug1: connect to address 192.168.1.105 port 22: Connection timed out
    ssh: connect to host 192.168.1.105 port 22: Connection timed out
    root@/ 2#


    Here's the nmap of my computer
    root@Mandi:/var/log# nmap 192.168.1.105

    Starting Nmap 4.53 ( Insecure.Org - Nmap Free Security Scanner, Tools & Hacking resources ) at 2009-08-22 12:26 CDT
    Interesting ports on 192.168.1.105:
    Not shown: 1709 closed ports
    PORT STATE SERVICE
    22/tcp open ssh
    111/tcp open rpcbind
    954/tcp open unknown
    2049/tcp open nfs
    6881/tcp open bittorent-tracker

    Nmap done: 1 IP address (1 host up) scanned in 0.393 seconds
    root@Mandi:/var/lo


    Anyone??

  2. #2
    Linux User
    Join Date
    Sep 2008
    Location
    UK
    Posts
    353
    Looking at this part of your post:
    root@/ 2# ssh -vv loy@192.168.1.105
    OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to 192.168.1.105 [192.168.1.105] port 22.
    debug1: connect to address 192.168.1.105 port 22: Connection timed out
    ssh: connect to host 192.168.1.105 port 22: Connection timed out
    root@/ 2#
    I think you need to check your pc settings. Something is blocking the connection on your pc or the pc's ssh settings don't allow connections.

  3. #3
    Just Joined! Loy Glenn's Avatar
    Join Date
    Sep 2008
    Location
    Houston,TX
    Posts
    89
    I wish that was the case...I can successfully make a ssh connection from any ssh client Anywhere (LAN or WAN, port forwarding setup correctly) to my pc.

  4. #4
    Linux User
    Join Date
    Sep 2008
    Location
    UK
    Posts
    353
    Are you sure your pc is not set up to use a non-standard port for ssh? If you can ping 192.168.1.105, then it's a port problem.
    Look at HowTos/Network/SecuringSSH - CentOS Wiki for some hints, if you already haven't.
    It also points you to the centos ssh setup at the end.

  5. #5
    Just Joined! Loy Glenn's Avatar
    Join Date
    Sep 2008
    Location
    Houston,TX
    Posts
    89
    I gave the nmap output of my pc - it shows port 22 --->

    PORT STATE SERVICE
    22/tcp open ssh

    But I verified it by connecting from other clients as well. PC is setup for port 22 (standard).


    ....The CentOS server has no problem accepting ssh clients. The problem is acting as a client to ssh to another computer. Any computer.
    Last edited by Loy Glenn; 08-24-2009 at 03:32 PM. Reason: completeness

  6. #6
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,281
    Check the firewall and ensure that NEW connection from the server are allowed on port 22.

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

  7. #7
    Just Joined! Loy Glenn's Avatar
    Join Date
    Sep 2008
    Location
    Houston,TX
    Posts
    89

    Solved

    Firewall shut down. Nothing.

    ADMIN on remote server haven't yet added my new WAN IP to lists of allowed clients. Figures - I only checked and re-checked my config 4 or 5 times. Thx for the help.
    Last edited by Loy Glenn; 08-24-2009 at 07:08 PM. Reason: solved

Posting Permissions

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