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. >> >> Just to state the obvious, have your tried something like: >> >> $ nc -v -z 123.123.123.123 22 >> 123.123.123.123 (ssh) open >> >> from a WAN client to make sure that the port is open? > > I don't have the nc comand. What package is it in? > >
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: # nc -w 3 -v -z 123.123.123.123 22 ool-43505ef2.dyn.optonline.net [123.123.123.123] 22 (ssh) : Connection timed out
