[FreeNX-kNX] Frontend for Terminal Services

[Kurt Pfeifle]

On Monday 27 September 2004 15:57, Luca Corti wrote:
> On Mon, 2004-09-27 at 12:57 +0200, Luca Corti wrote:
> > From: Doug Burks <mubley at gmail.com>
> > To: Luca Corti <luca.corti at tiscali.it>
> > Cc: <freenx-knx at kde.org>
> > Subject: Re: [FreeNX-kNX] Frontend for Terminal Services
> > 
> > You've already got FreeNX installed and working, so to get FreeNX to
> > frontend Windows Terminal Services, you'll need the following:
> > 1)  nxdesktop on the FreeNX server
> > 2)  NX client configured to access a Windows Terminal Server
> 
> This is not completely clear to me. How the nx server knows about the
> rdp one?

Because you tell the NX Client (by typing in its name and your auth
credentials), and because the NX Client then tells the NX Server,
and because the NX Server than contacts the RDP server (and if it
fails either the name or the credentials you used were wrong)   ;-)

Your NX Client contacts the NX Server the usual way: port 22, via
SSH.

[....]

> > -Start the NX Connection Wizard.
> > -NX Connection Wizard Welcome screen appears.  Click Next.
> > -Session screen appears.  Enter the requested data and click Next.
> > -Desktop screen appears.  Click the first drop-down box and select
> > Windows.
> > -Settings window appears.  Type the hostname of the Windows Terminal
> > Server.  (The FreeNX server has to be able to resolve this hostname.) To
> > keep this first test as simple as possible, leave the rest of the
> > options at their default ("Show the Windows login screen" and "Run
> > desktop") and click OK.
> 
> Ok, I've configured this, but how can the client know that I want to
> pass through my nx server instead of directly connecting to the windows
> server? Also, on which port should I connect? SSH (22) or TS (3389) ?

See above.

> > -Back at Desktop screen, click the checkbox next to "Enable SSL
> > encryption of all traffic" and click Next.
> > -Configuration Completed screen appears.  Click Finish.
> > -NoMachine login window appears.  Enter login and password, and click
> > Login.
> > -The NX client will login to the NX server and then launch nxdesktop to
> > connect to the Windows Terminal Server you specified.
> > -If all goes well, you should have an NX-boosted Terminal Services
> > session!
> 
> I can't connect to the server. I get "NX server has refused the
> connection" the and in the details window:

So you can't even run remote X11 sessions?

> NX> 203 NXSSH running with pid: 1640
> nxssh: connect to address ip.address.ofmy.termsrv port 22: connection
> refused

Nooooooooo.......

You should *always* connect to ip.address.ofyour.nxserver port 22.

> Why the ssh port on the windows host should be open?

It shouldnt. NX Server will contact Windows server on its own.

!. Start NX Client
2. Insert data of your *NX* server on 1st tab
3. Open 2nd tab.
4. Select "Windows desktop".
5. Click "Settings...."
6. Insert data of your Windows server on the new dialog
7. Save and connect and have fun.

Please note, that the NoMachine website as this and some other
useful documentation on 

   http://www.nomachine.com/howto/rdp-session.php

and

   http://www.nomachine.com/usage.php

and

   http://www.nomachine.com/documentation.php

You must have overlooked it.

> If I change the target port to 3389 I get "Connection error":
> 
> NX> 203 NXSSH running with pid: 3608
> NX> 200 Connected to address: ip.address.ofmy.termsrv port 3389
> 
> 
> I fear I miss something. I thought the setup was something like:
> 
> client (nomachine client) -> frontend (freenx) -> backend (termsrv)

No, it is like this:

  NoMachine client --> FreeNX/NoMachine NX server --> backend (termsrv)

> with the client knowing nothing about the backend windows host.

On the contrary. Initially the NX server knows nothing about the
windows host. It is *you*, the user who must know where you wanna
connect to. Tell the client about the Terminal Server and the
Client will ask the NX Server to proxy the connection.

> thanks
> Luca

> CONFIDENTIALITY NOTICE
> This message and its attachments are confidential and may also be 
> privileged. If you are not the named recipient, please notify the 
> sender immediately, delete this message and do not disclose the 
> contents to any other person, do not use it for any purpose or 
> store or copy the information in any medium.    

OK, ok. But in reverse, I allow you to use any info you find in
this mail's body freely. (I dont allow you to use the mail's
headers). The mail's content isnt confidential and not privileged
at all.

Hey, do you really think that your "NOTICE" does anything in favor
of your privacy???

Cheers,
Kurt