Acces CODA via NX

L'accès TSE direct est lent. Idée : proposer un accès NX, réputé plus rapide.

Principe :

• un serveur freenx à Montréal, accessible depuis le RPV
• ce serveur sera un proxy NX/RDP vers le serveur reflets-tse

Comment faire :

• inspiration : http://www.linuxjournal.com/article/8342#comment-53601

• serveur freenx : https://help.ubuntu.com/community/FreeNX

• voir paquet freenx-rdp dans https://launchpad.net/~freenx-team/+archive/ppa

Test :

• testé en local sur ma machine (ThomasNoël) : un proxy FreeNX/RDP. Ca marche, y compris le copier-coller vers macro OOo. Non testé : l'impression.

• test à faire en vrai : un proxy à Montréal (le serveur freenx n'est dispo que pour Ubuntu => tester d'abord avec une Ubuntu karmic)

Extrait de http://www.linuxjournal.com/article/8342#comment-53601 :

Using VNC I can access Windows computers from my Linux desktop. Can FreeNX do that?

Yes, it can.

However, it does not done directly. NX clients need an NX or FreeNX server that acts as a proxy. The (Free)NX proxy can then relay the NX session to a nearby VNC/everything or RDP/Windows server.

Over low bandwidth/high latency links (like a 56k baud dialup modem), this is usable and way faster than trying to directly access a remote host via vncviewer or rdesktop.

NX and FreeNX proxies/servers can run on Linux, FreeBSD and Solaris.

• Connecting an NX client to a Windows Terminal Server:

   Xdisplay/NXclient <--(NX protocol)--> NXserver-proxy/nxdesktop <--(RDP protocol)--> WindowsTerminalServer 

The Windows NX client ships including an X server that provides the Xdisplay. The Linux/Unix NX clients use the native Xdisplay of their hosting OS. The "nxdesktop" part of the NXserver-proxy is a modified and improved derivate of "rdesktop" and takes care of the "RDP <--> NX" protocol translation.

Cheers,

Kurt Pfeifle (FreeNX Developer Team, KDE Project Contributor)