[FreeNX-kNX] Nomachine 4 out....

[Marco Passerini]

In fact, now I understood how I managed to get a terminal on the server 
at first. In the new client you can choose the following:

* create a new virtual desktop
* create a new custom session

For former opens fluxbox, the latter opens a rootless  terminal on the 
server.

This is very bad for my use case. I need to investigate more.



I still didn't understand if it's possible to use a custom shared key at 
all, there seem to be no field where to enter those anymore.


On 2013-10-17 15:45, Marco Passerini wrote:
> Hi,
>
> Apparently the commercial version of Nomachine 4 is out. I installed the
> new client for RHEL6 and the first impression was not good at all.
>
> I would like to start saying that I have 2 NX servers which are used as
> "bridges" to connect to other servers, so the users can't SSH into these
> NX boxes, they cannot open local terminals and access local files, they
> can just open terminals to other machines. This is done with a custom
> Fluxbox/NX configuration. One of the servers has the FreeNX version, one
> of the has the 3.5 commercial version.
>
> So, everything worked fine with the old client but the new client does
> not work well at all, I suggest other people to test it against your
> installations.
>
> * The GUI is a mess. Totally bad design.
> * At the first login to the server with the 3.5 commercial server
> version, I got a rootless terminal to the NX server itself, and I
> couldn't see  the Fluxbox desktop at all. This is a security problem for
> my setup.
> * Then I opened Matlab, closed the session and when I logged it again
> the image and resolution was totally messed up.
> * I closed the session, opened it again, and this time I could see the
> Fluxbox desktop as it was supposed to be!
> * After this it always showed the Fluxbox desktop.
> * Resizing the window does not work well, the image becomes "dirty" with
> some strange lines and pixels which should not be there.
> * Now when I log in it says that there's a guest connected to my
> session, with my own username.
> * I tried to connect with the new client to my old FreeNX servers, and
> it didn't work at all, I'm not sure if it's because of my configuration
> or because of some block they implemented to cut out the opensource
> version.
> * I couldn't find
>
> I will contact the Nomachine support about these issues, but I doubt
> they will be able to fix these issues any soon.
>
> Please share your experiences with the new client!
>
>
> Marco
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________


-- 
Marco Passerini
System Specialist
CSC  IT Center for Science
Mobile: +358 50 381 8424
E-Mail: marco.passerini at csc.fi