[sllug-members]: SSH question

[Mark K. Spute]

I ran

ssh -p 22 root at 127.0.0.1

from the server console and it gave:

ssh: connet to host 127.0.0.1 port 22: Connection refused

I tried it again with:

ssh -p 3022 root at 127.0.0.1

and I got:

The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.
RSA key fingerprint is 23:3f: . . .
Are you sure you want to continue connecting (yes/no)?

Does this mean it is listening on this port, but it doesn't recognize 
itself?

Mark

Roger Smith wrote:
> On Thursday 17 April 2008 10:13:56 am mark.k.spute at l-3com.com wrote:
>> I didn't restart the server but I did
>>
>>  service sshd reload
> 
> restart the service. Reload, in this case, is probably not sufficient. Make 
> sure iptables allows traffic through that port. If you run "iptables -L" and 
> get a list of ports that are open then you are most certainly blocking that 
> port, unless you have already configured iptables to allow traffic to the 
> port.
> 
> The ssh configuration is pretty straight forward. The only mistake I can see 
> someone making is confusing the client configuration file "ssh_config" with 
> the daemon configuration file "sshd_config".  
> 
> try "ssh -p 22 user at server" and see if ssh is still listening on port 22.
> from the server try  "ssh -p 3022 user at 127.0.0.1".  Localhost is usually not 
> firewalled, and sshd by default listens on all interfaces including the 
> loopback device.
> 
> a) sshd is running on the old port 22 because the service has not been 
> restarted
> 
> b) the new port is firewalled.
> 
> c) sshd is not running "ps -A|grep sshd"
>