| 1 |
On 02/24/2011 08:08 PM, dhk wrote: |
| 2 |
> On 02/24/2011 06:30 PM, Mick wrote: |
| 3 |
>> On Thursday 24 February 2011 21:51:56 dhk wrote: |
| 4 |
>> |
| 5 |
>>> Thanks, but I've tried that. ssh'ing to the hostname and loopback |
| 6 |
>>> address work. However, when I go out to the WAN it doesn't. So I can't |
| 7 |
>>> ssh user@123.123.123.123 even though I have port 22 open on the switch |
| 8 |
>>> for my ip. |
| 9 |
>> |
| 10 |
>> Just to state the obvious, have your tried something like: |
| 11 |
>> |
| 12 |
>> $ nc -v -z 123.123.123.123 22 |
| 13 |
>> 123.123.123.123 (ssh) open |
| 14 |
>> |
| 15 |
>> from a WAN client to make sure that the port is open? |
| 16 |
> |
| 17 |
> I don't have the nc comand. What package is it in? |
| 18 |
> |
| 19 |
> |
| 20 |
|
| 21 |
The nc command does nothing when run from the same host I'm trying to |
| 22 |
ssh in to. I'm not sure what that means other than it can't make a |
| 23 |
connection. With the -w option I get: |
| 24 |
|
| 25 |
# nc -w 3 -v -z 123.123.123.123 22 |
| 26 |
ool-43505ef2.dyn.optonline.net [123.123.123.123] 22 (ssh) : Connection |
| 27 |
timed out |
Archives