|
there's a lot to consider here...
- is the computer you're ssh-ing from on the same network as your host?
- do you know that port 22 is not firewalled either on the way out of the other computer, or somewhere in between the two, or on your linux host?
- you could try ssh-ing from the host itself:
ssh localhost
- this would tell you at least that sshd is working fine, and that it's probably some network/firewall issue
- there are lots of things in the sshd_config file that could trip you up - look especially in the authorisation section
- you may need to add to the hosts.allow file - though this would be specified in the sshd_config file
- have you got logging turned on on the host? have a look at sshd_config for SyslogFacility to find out, then see what's in /var/log/auth.log or /var/log/syslog (tho i'm not familiar with suse, so it might be different files or directory). this might tell you that you're reaching the host, but failing to authorise for some reason.
but it's probably a firewall issue. does suse install with an active firewall?
are the two machines separated by a router at home? you will need to allow outside traffic on port 22 into your network/computer
and, if you are opening up your network for the first time, do it carefully, it's a big bad world out there. read about network security.
|
