How to enable ssh service on suse 10?
 

I type "service ssh start", "command not found"

I enter etc/rc.d/ , ./sshd start, It's ok

But I still can not ssh to the server by putty?What should I do

Thanks!

Is there a firewall on the machine?
If so disable first and see if you can login.

Here a good link to setup ssh. http://www.suso.org/docs/shell/ssh.sdf

SSH service is installed if you took the default installation packages. You just have to allow the SSH service through your firewall. Yast Modules/Security and Users/Firewall. Then for your services select SSH. This opens TCP port 22 which is the default SSH port.

You can test your ssh by going to a Konsole and typing "ssh localhost" and it will ssh to your machine through the loopback device "lo". It should prompt for your password which is the same user account as what you typed that command. It should accept your password and then you can just type "exit" to quit the SSH connection.

Hope this helps! :D

Oh I think default , "service" command set is only available on RedHat and Fedore distribution so you can not use it on SUSE until you setup (ie , install) it .
On SUSE , first you must check sshd is available (by using locate or which command , for example which sshd ) . If it exists , all you have to do to enable sshd (I mean ssh server not ssh client) is type sshd at your console . That's all . After that , you can using secure shell (ssh command) to log on your computer which enable service ssh ( ie , ssh server or sshd) .

Hope it help you ,
nguyennh

ssh is enabled by default (unfortunately) in SUSE. You will have to configuere it only.

Thank you guys, It's the problem of firewall. I have figure out it.
Appreciate

I was just reading
 

Useful information using suse,
type as root user that is type,
chkconfig without arguments if you want
but chkconfig sshd on to start sshd at
start up and alternativly
chkconfig sshd off to set it back.

This is not only hard to read/unserstand, but is on a FOUR YEAR OLD THREAD that has been closed quite a while. Please don't reopen old threads.

actually his comment solved my problem!