[FreeNX-kNX] Chaining nxservers with ENABLE_SERVER_FORWARD

[Bryan Cole]

I want to open an nx-session to a machine via a gateway server but I
can't get it to work. I.e. with three machines:

A->B->C

A is the nxclient machine
B is the gateway, running an nxserver (freenx)
C is the server I want to log in to, and is also running a freenx server

Openning an nx-session on B, from A works fine. However, when I set the
"ENABLE_SERVER_FORWARD" option in B's node.conf file, in order to log
into C, I always get the following error:

NX> 203 NXSSH running with pid: 6142
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: xx.xxx.xx.xxx on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 280 Ignoring EOF on the monitored channel
NX> 280 Ignoring CLOSE on the monitored channel
Pseudo-terminal will not be allocated because stdin is not a terminal.
ssh: xxx-C-xxx:22: Name or service not known
Killed by signal 15.

where xxx-C-xxx is C's hostname. A is connecting to B ok. I can ssh from
B to nx at C ok as well. As far as I can see, the ssh setup (certificates
etc.) is fine on all machines. I can ssh from A->B and B->C as user 'nx'
with no problems. There are no errors I can see in the ssh logs. It
looks like a bug in the forwarding mechanism. Has anyone else got this
to work?

BTW., I'm using SSH for all communication. (everything over port 22)

Any ideas?
Bryan