> linux:~ # ssh 127.0.0.1 > ssh: connect to host 127.0.0.1 port 22: Connection refused
You mean sshd is actually running, but doesn't want to let you log in? That's an entirely different situation. It's possible to restrict the source IPs from which logins are allowed, as well as users who are allowed to log in. This is configured in /etc/ssh/sshd_config. root is often not allowed to log in. > Just to prove to you doubters that it really does kind-of connect OK > to port 22, The output from netstat -antp showing sshd listening on port 22 would have been sufficient to prove that the daemon is running and waiting for connections. > I even tried "rcSuSEfirewall2 stop" before trying to start sshd, Very good idea, but use "SuSEfirewall2 stop" for this service. Btw the packet filter and sshd are independent of each other, though in some configurations SuSEfirewall hunts for locally bound ports to disable access. For packets to reach sshd, a) they must pass the packet filter, and b) sshd must be listening. Whether sshd then lets you log in is a totally different question again ;) HTH, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
