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

Fri Dec 2 22:59:13 UTC 2005

Hello All,

There is some advancement with connecting to Windows machine via FreeNX server acting as a proxy.

I've enabled IP forwarding and now trying to connect to XP machine, I'm starting to get the initial screen of !M for a few seconds after which I got message "The connection with remote server was shut down Please check the state of your network connection".

Lookin at the logs of /var/log/nxserver.log I get:

-- NX SERVER START: -c /usr/bin/nxserver
HELLO NXSERVER - Version 1.4.0-44 OS (GPL)
NX> 105 hello NXCLIENT - Version 1.5.0
NX> 134 Accepted protocol: 1.5.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: myusername
NX> 102 Password: 
Info: Auth method: passdb ssh userdb check

NX> 103 Welcome to: neroserver user: myusername
NX> 105 listsession --user="myusername" --status="suspended,running" --geometry="1024x768x16+render" --type="windows"
NX> 127 Sessions list of user 'myusername' for reconnect:

Display Type             Session ID                       Options  Depth Screen         Status      Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------

NX> 148 Server capacity: not reached for user: myusername
NX> 105 startsession --session="nero" --type="windows" --cache="8M" --images="32M" --cookie="******" --link="adsl" --kbtype="pc102/us" --nodelay="1" --encryption="1" --backingstore="when_requested" --geometry="1021x746" --media="0" --agent_server="82.74.41.136" --agent_user="" agent_password="******"domain.haifa.ac.il"  --screeninfo="1021x746x16+render" 

&session=nero&type=windows&cache=8M&images=32M&cookie=******&link=adsl&kbtype=pc102/us&nodelay=1&encryption=1&backingstore=when_requested&geometry=1021x746&media=0&agent_server=82.74.41.136&agent_user=&agent_password=******&screeninfo=1021x746x16+render&clientproto=1.5.0&user=lkolchin&userip=212.132.87.145&uniqueid=45F63697F1DC0074ADAEE5C9B2FA5B4B&display=1000 
Password: 
NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL)
NX> 700 Session id: nero-1000-45F63697F1DC0074ADAEE5C9B2FA5B4B
NX> 705 Session display: 1000
NX> 703 Session type: windows
NX> 701 Proxy cookie: 8d505c87363677a80a7a3f653b7914f9
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 8d505c87363677a80a7a3f653b7914f9
NX> 704 Session cache: windows
NX> 707 SSL tunneling: 1
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1005 Session status: suspended
NX> 1001 Bye.

What seems to be the problem here?

Best Regards,
Leon Kolchinsky

-----Original Message-----
From: Verner Kjærsgaard [mailto:vk at os-academy.dk]
Sent: Fri 02.12.2005 22:35
To: User Support for FreeNX Server and kNX Client
Subject: Re: [FreeNX-kNX] Connecting to Windows computers from Linux viaFreeNX

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

------------------------------
_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX at kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx