[FreeNX-kNX] FreeNX server behind NAT

[Doug Burks]

Hi Leon,

The easiest way to do this is to make sure that "Enable SSL encryption
of all traffic" is checked (enabled) on the NX client.  This forces NX
to use SSH for all of its communication.   So then the trick is to
make sure that you can SSH to the FreeNX server.  As long as you can
do that, then you should be able to establish a FreeNX session.

You say that you have configured SSH to accept connections on port 22
and 23; have you tried actually connecting to both ports to verify
that this works?  If so, then fire up your NX client, click the
Configure button, set Port to 23 (on the General tab), and make sure
that "Enable SSL encryption of all traffic" is checked (on the
Advanced tab).  Then try logging in.

If it doesn't work, you might try editing /usr/bin/nxserver and changing:
SSHD_AUTH_PORT="22"
to:
SSHD_AUTH_PORT="23"
and see if that helps.  

Let us know how it goes.

Thanks,
Doug


On Wed, 29 Sep 2004 17:08:00 -0400 (EDT), Leon Bukhman <leon at lbsharp.com> wrote:
> I am trying to connect to my FreeNX server from work but I am having
> problems establishing the connection. The problem is that the server is
> behind a NAT box and the client is also behind a firewall (which blocks
> port 22).
> 
> I set up SSH to accept connections of ports 22 and 23 so that I can
> connect from work. Is there a way to configure FreeNX to listen on both
> ports as well?
> 
> Also, since the server is behind a NAT box, what is the minimum number of
> ports that I would need to forward to get it working? (Is it enough to
> just forward port 5000? And how can I change which port ranges are used by
> NX?)
> 
> Thanks in advance
> 
> Leon
> 
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>