[FreeNX-kNX] Connecting to Windows computers from Linux via FreeNX

[Verner Kjærsgaard]

Fredag 02 december 2005 20:08 skrev lkolchin at univ.haifa.ac.il:
> Hello All,
>
> I've read Kurt's post
> (http://www.linuxjournal.com/article/8342#comment-53601) on connecting to
> Windows computers from Linux desktop using FreeNX server as proxy. Now I'm
> trying to implement this scenario.
> Actually I'm interesting in the following 2 scenarious:
> Connecting an NX client to a VNC server:
>
> Xdisplay/NXclient <--(NX protocol)--> NXserver-proxy/nxviewer <--(RFB
> protocol)--> VNCserver
>
> Connecting an NX client to a Windows Terminal Server:
>
> Xdisplay/NXclient <--(NX protocol)--> NXserver-proxy/nxdesktop <--(RDP
> protocol)--> WindowsTerminalServer
>
> I've installed FreeNX server on SLES9 machine and set it up with:
> nxsetup --install --setup-nomachine-key
> nxserver --adduser <username>
>
> And it works OK, I can connect to it from Linux/Windows Clients.
>
>
> Now I go to /etc/nxserver/node.conf on the server and make the following
> changes:
>
> #########################################################################
> # Forwarding directives
> #########################################################################
>
> # FreeNX with ENABLE_SERVER_FORWARD="1" will automatically forward all
> # connections to the host specified in SERVER_FORWARD_HOST with the
> # secret key SERVER_FORWARD_KEY.
> #
> # This allows to have a "chain" of NX Servers. Note that you will need to
> # use "SSL encryption" for all connections.
>
> ENABLE_SERVER_FORWARD="1"
> SERVER_FORWARD_HOST="62.72.41.136"
> SERVER_FORWARD_PORT=3389
> #########################################
>
> I'm configuring a Windows Terminal Server session like in this
> http://www.nomachine.com/howto/rdp-session tutorial, and trying to login
> from the client on Linux,and it failes with the following log on the client
> machine:
>
> NX> 203 NXSSH running with pid: 6614
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 200 Connected to address: 62.72.41.20 on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> Warning: Identity file /usr/NX/share/client.id_dsa.key does not exist.
> 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: 132.74.41.136:3389: Name or service not known
> Killed by signal 15.
> -----------------------------------
>
>
> Please instruct me how to make it work?
>
>
> Best Regards,
> Leon Kolchinsky
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx


I've done like this;

on the Linux server, I put an icon onto the desktop of my account.  It 
launches rdesktop with a bunch of parameters, one being -f (full screen). 
This launches the screen of either the windows application called (with 
rdesktop) or the desktop of the MS-Windows 2003 terminal server.

See "man rdesktop"

Hope this helps!

-- 
------------------------------
Med venlig hilsen/Best regards
Verner Kjærsgaard
Denmark

------------------------------