From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Pt7l8-00010D-OP for garchives@archives.gentoo.org; Sat, 26 Feb 2011 00:11:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 57F391C061 for ; Sat, 26 Feb 2011 00:11:41 +0000 (UTC) Received: from mail-ww0-f41.google.com (mail-ww0-f41.google.com [74.125.82.41]) by pigeon.gentoo.org (Postfix) with ESMTP id 0782FE0794 for ; Fri, 25 Feb 2011 23:08:11 +0000 (UTC) Received: by wwb17 with SMTP id 17so1216951wwb.4 for ; Fri, 25 Feb 2011 15:08:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:reply-to:to:subject:date:user-agent :references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=zLe9PMu3nyFBio5I8o8SMUlAtqHcWhMKV6HN3AdDLeM=; b=L8zBciIhXdEuuV6Mswv2ZgT86sd9C+YGXx/XfkVVNNmVNgH19bdUaNpGqj3kC3fdw3 IcuZP0X9j9hdKwDlrlnYrPBJreStlq0L7PF5Xc5LuGSgVE7YaoPkx+ikY8WzONaXrkky 34uN8+SLQUaz4P7z1ERKAWbuFz+TZcj2IlTuY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=bB/DaIycIIvETKK9ZAiDx/c0sXYvepmmezPmM6PrDHKsEeNO/nKjcA8BSazdtS6eXV yFDveeeu8CNTQ0v6Jjsb/0rSACHDwX4GvR7fvxO86A47bR3gAtABKzSeuw+ZW+iY3Rz0 89mnpL3isGv8p0WxpZl9IyKwE+BdyjrLm4gfk= Received: by 10.227.136.66 with SMTP id q2mr2738252wbt.58.1298675290913; Fri, 25 Feb 2011 15:08:10 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id f27sm963497wbf.7.2011.02.25.15.08.08 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 25 Feb 2011 15:08:08 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ssh problem Date: Fri, 25 Feb 2011 23:08:11 +0000 User-Agent: KMail/1.13.5 (Linux/2.6.36-gentoo-r5; KDE/4.4.5; x86_64; ; ) References: <4D63A165.4000007@optonline.net> <4D6700F5.30504@optonline.net> <4D679C02.6030408@optonline.net> In-Reply-To: <4D679C02.6030408@optonline.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart81183034.o9zc3dM2jX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201102252308.24970.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: 3854751ac9f69f61c1b140ce7e02e030 --nextPart81183034.o9zc3dM2jX Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Friday 25 February 2011 12:09:38 dhk wrote: > On 02/24/2011 08:08 PM, dhk wrote: > > On 02/24/2011 06:30 PM, Mick wrote: > >> On Thursday 24 February 2011 21:51:56 dhk wrote: > >>> Thanks, but I've tried that. ssh'ing to the hostname and loopback > >>> address work. However, when I go out to the WAN it doesn't. So I > >>> can't ssh user@123.123.123.123 even though I have port 22 open on the > >>> switch for my ip. > >>=20 > >> Just to state the obvious, have your tried something like: > >>=20 > >> $ nc -v -z 123.123.123.123 22 > >> 123.123.123.123 (ssh) open > >>=20 > >> from a WAN client to make sure that the port is open? > >=20 > > I don't have the nc comand. What package is it in? >=20 > The nc command does nothing when run from the same host I'm trying to > ssh in to. I'm not sure what that means other than it can't make a > connection. With the -w option I get: >=20 > # nc -w 3 -v -z 123.123.123.123 22 > ool-43505ef2.dyn.optonline.net [123.123.123.123] 22 (ssh) : Connection > timed out OK, this proves that you have a connectivity problem. If the port was open= =20 and there was a ssh server listening on port 22 for connections you would g= et=20 an "open" response. BTW, nc is not necessary, you could use e.g. telnet to check the connection: $ telnet 123.123.123.123 22 SSH-2.0-OpenSSH_5.8p1-hpn13v10lpk If instead of the above you are getting no response and you are confident t= hat=20 you have not defined something other than port 22 for connections to your s= sh=20 server, then there is perhaps a firewall problem? =2D-=20 Regards, Mick --nextPart81183034.o9zc3dM2jX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk1oNmgACgkQVTDTR3kpaLY3zwCghMFsCVwpUHGpQDWdUqNyLKj+ TKEAnjVLcwSOCKTA9cUOZeBGjIg7mY+6 =jDla -----END PGP SIGNATURE----- --nextPart81183034.o9zc3dM2jX--