[FreeNX-kNX] Unexpected timeout connecting

[Geoff Hoff]

On Wed, 24 Nov 2004 16:45:01 +0100, Gian Filippo Pinzari
<pinzari at nomachine.com> wrote:
> > The nx at remote -> user at remote ssh is transparent to the process and may
> > not be used in the commercial version.
> 
> May you better explain this point? As far as I understand you are
> talking about the way FreeNX is implemented in the latest version.
> Sorry if I get this incorrectly. Just guessing from previous mes-
> sages in this list.

Yes, this is based on the latest FreeNX code.  I have not looked
closely at the No Machine server.  I suspect that they are close in
behavior, but may differ in implementation.

> In the latest version FreeNX logs in to the node using the real
> password of the user instead of the private server key. This is
> problematic because the NX server doesn't store the password
> and so it would not be able to perform any scheduled maintenance
> once the user has disconnected from the node.

Interesting point about the maintenance.  I wasn't obvious to me why
the nx account was being used.  I assumed it was for future features.

> > Also if using vnc or rdp instead of your X desktop replace nxproxy
> > with nxviewer or nxdesktop respectively.
> 
> Replace nxagent, instead ;-). nxagent, nxviewer and nxdesktop
> all use nxcomp/nxproxy to implement the NX transport, while the
> other nxproxy peer runs on the client.

You got me  <grin>.  That is what I intended to say.