Originally Posted by SubCore

the phone doesn't respond to pings, so that's expected.

make sure the ssh daemon is running - type in xterm:

Code:

ps aux | grep ssh

you should get a line containing "sshd" and ":22" somewhere. if not, your daemon isn't running, and you can start it by rebooting the device or by issuing

Code:

sudo gainroot
initctl sshd start

Originally Posted by Crogge

Well it says "5131 root 3884 S /usr/sbin/sshd -D" so it seems to be ok?

Originally Posted by SubCore

yes, seems ok.
now try

Code:

netstat -pan | grep ssh

that lists network connections / listeners, and that's where you should find a line with ":22", indicating that sshd listens on port 22 (sorry that i wrote :22 should be seen with ps aux )

then you can try

Code:

ssh root@127.0.0.1

on the device to check if local connections work.

if local connections work but you still can't connect from your laptop/pc, then we'll have to install sysklogd and enable logging for ssh.

Originally Posted by Crogge

tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN

Originally Posted by SubCore

hehe sorry i'm used to certain parameters i use on desktop / server systems all the time. -pan is one of them

":ssh" is equal to the ":22" i was talking about, the -n parameter for netstat should trigger the display of port numbers instead service names.
anyhow...

do you have some sort of firewall configured which may be blocking port 22 on your wlan?
you could try to change the port on which sshd listens:

Code:

sudo gainroot
cd /etc/ssh
cp sshd_config sshd_config.bak
cat sshd_config.bak | sed 's/Port 22/Port 2022/' > sshd_config
initctl stop sshd
initctl start sshd

with these commands, you create a backup file of your current config, and then use the tool "sed" to change the value for Port from 22 to 2022.
(or you edit the file sshd_config some other way, with vim f.ex.).

now you can try connecting to the device using the new port:

Code:

ssh -p 2022 root@n900.ip

Originally Posted by Crogge

Any idea why the SSH server accepts only local connections?

Originally Posted by Crogge

I tested already another SSH client and my notebook, even my N95 to be sure that the problem is not on the client side. That displayed the following error "Host unreachable (-191)".