how frequently does the letter o appear in:
q: ssh: no route to host im failing to set-up an ssd on port 9922. with standard configuration on port 22 everything works fine. then i change the port to 9922 by adding this line to ths sshd_config file:
port 9922

i can connect to the server in the lan on port 22 without prolems. after switching to port 9922 i get the following ouptput:
# ssh -vvv -p 9922 root@192.168.26.153
openssh_4.3p2, openssl 0.9.8e-fips-rhel5 01 jul 2008
debug1: reading configuration data /etc/ssh/ssh_config
debug1: applying options for *
debug2: ssh_connect: needpriv 0
debug1: connecting to 192.168.26.153 [192.168.26.153] port 9922.
debug1: connect to address 192.168.26.153 port 9922: no route to host
ssh: connect to host 192.168.26.153 port 9922: no route to host
#

and nmap -p 9922 192.168.26.153 gives:
# nmap -p 9922 192.168.26.153

starting nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2012-06-11 08:09 cest
interesting ports on 192.168.26.153:
port     state    service
9922/tcp filtered unknown
mac address: 4a:34:e7:11:9f:22 (unknown)

nmap finished: 1 ip address (1 host up) scanned in 0.184 seconds
#

any ideas whats missing?
ifconfig on the target machines gives:
eth0      link encap:ethernet  hardware adresse 4a:34:e7:11:9f:22  
          inet adresse:192.168.26.153  bcast:192.168.26.255  maske:255.255.255.0
          inet6 adresse: fe80::4834:e7ff:fe11:9f22/64 g?ltigkeitsbereich:verbindung
          up broadcast running multicast  mtu:1500  metric:1
          rx packets:2723010 errors:0 dropped:0 overruns:0 frame:0
          tx packets:552 errors:0 dropped:0 overruns:0 carrier:0
          kollisionen:0 sendewarteschlangenl?nge:1000 
          rx bytes:561183811 (535.1 mib)  tx bytes:52703 (51.4 kib)
          interrupt:24 

lo        link encap:lokale schleife  
          inet adresse:127.0.0.1  maske:255.0.0.0
          inet6 adresse: ::1/128 g?ltigkeitsbereich:maschine
          up loopback running  mtu:16436  metric:1
          rx packets:0 errors:0 dropped:0 overruns:0 frame:0
          tx packets:0 errors:0 dropped:0 overruns:0 carrier:0
          kollisionen:0 sendewarteschlangenl?nge:0 
          rx bytes:0 (0.0 b)  tx bytes:0 (0.0 b)

and route -n:
# route -n
kernel ip routentabelle
ziel            router          genmask         flags metric ref    use iface
192.168.10.0    192.168.26.1    255.255.255.0   ug    0      0        0 eth0
192.168.26.0    0.0.0.0         255.255.255.0   u     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     u     1002   0        0 eth0
0.0.0.0         192.168.26.4    0.0.0.0         ug    0      0        0 eth0
# 

iptables -l returns:
# iptables -l
chain input (policy accept)
target     prot opt source               destination         
accept     all  --  anywhere             anywhere            state related,established 
accept     icmp --  anywhere             anywhere            
accept     all  --  anywhere             anywhere            
accept     tcp  --  anywhere             anywhere            state new tcp dpt:ssh 
reject     all  --  anywhere             anywhere            reject-with icmp-host-prohibited 

chain forward (policy accept)
target     prot opt source               destination         
reject     all  --  anywhere             anywhere            reject-with icmp-host-prohibited 

chain output (policy accept)
target     prot opt source               destination         
# 


a: you must likely have selinux enabled at your server. if you dont need it, disable it temporarily with setenforce 0 or permanently by modifying /etc/selinux/config file. 
if you want to use selinux, make it allow sshd to bind to port 9922:
semanage port -a -t ssh_port_t -p tcp 9922


a: while it is not a smart idea to stop the firewall i would propose to start the firewall and allow incomming port 9922 by 

/sbin/iptables -a input -p tcp --dport 9922 -j accept


a: for me was a combo of selinux and firewall, i found the solution doing in this way: 
as already proposed, relaxing selinux: 
semanage port -a -t ssh_port_t -p tcp 9922

and after that, changing even the firewall permission:
sudo firewall-cmd --zone=public --add-port=9922/tcp --permanent
sudo firewall-cmd --reload

these two changes make me possible to access to the server with the new ssh-port 

a: you can have multiple port lines in your sshd.conf, e.g.
port 22
port 2222
#protocol 2,1
protocol 2
#addressfamily any
#listenaddress 0.0.0.0
#listenaddress ::

i typically do this because ill have an external firewall/nat open on the alternative port, but will want internal systems to hit the server on the traditional port 22. 
please make sure you restart the ssh daemon (service sshd restart) following any configuration file changes.
what happens if you nmap -p 9922 192.168.26.153? does it show the port open?
the error in your ssh client debug output should be connection timed out instead of no route to host. whats in between you and the target system?

user
In that passage, there are 208 occurrences of the letter "o."
assistant