#Nomachine review software#

So we introduced a further dialog, shown at the time the users connects, asking if he/she wants to resize the remote desktop.

#Nomachine review software#

Unfortunately the new behavior seem to scare the old users (which rarely used the software for collaboration since access to the physical display was quite limited). If there is somebody in front of the screen, this somebody doesn't want the desktop to be resized to a different resolution when a buddy connects. Adapting the remote desktop resolution to the client may appear a no-brainer, but try to think of NoMachine used as a collaboration tool and not just as a terminal server. There are buttons to set 1:1 and also let the remote desktop adapt to the client but this is not automatic. The default is to scale the remote desktop to the client window. One of the changes included in the version 4.1 (to be released on Monday) is to allow users to change the resolution of the remote desktop automatically as they connect. Sometimes I get a scaled display with unreadable text, as the physical system console is a higher resolution than the MoMachine console I am trying to create. I wish you the best but I just don't see NoMachine 4 being something I'll be picking up and using in the future.Įvery time I use the new NoMachine client I end up struggling through the new GUI only to get something that is not quite what I want. It seems that you are trying to move towards some kind of terminal services/VDI type of product, but by completely overhauling your product and closing off the source you have effectively left behind a lot of your established presence and good will. Perhaps I need to spend more time with it and learn its interface and configuration more thoroughly, but with limited time The new version, which I have attempted to use several times, has a confusing out of the box setup with a myriad of sub-menus and no clear linear path to setup a simple connection as I had before. FreeNX 3.5 was everything I needed for that purpose. The initial configuration was very simple and gave me reliable and consistent access to servers over low bandwidth, high latency links. It also defaults to something other than SSH, which doesn't normally work since I have rather well defined firewalls in place and NX's ability to piggy back on SSH made it fast, easy, and secure to setup.Īll I want is a fast, easy, and secure remote console I can use to log into a server that requires a GUI to run, such as RDHS or 389 LDAP console and then get out. I appreciate your comments and willingness to discuss your product.Įvery time I use the new NoMachine client I end up struggling through the new GUI only to get something that is not quite what I want. But in 6 months from now it will be a matter of starting the client and connecting to one of the servers showing in your roster, a step forward compared to having to mind the protocol to use, the IP address, etc. These functions are not available yet (mDNS discovery is in testing and will be part of the 4.1, planned for the end of the year, while the directory service and NAT traversal will take a bit more), so I understand that, compared to the simple combo box of the 3 it shows more information and thus can appear more complicated. New computers are automatically showing in the roster based on mDNS discovery or a global directory and NAT traversal service we currently have under development.

All the new GUI is designed to be 'dynamic'.

Then there is the initial GUI, by which you must choose the computer to connect to. It is more configurable and so more 'complex', but this sense of complexity should disappear as soon as you start to use it. The biggest change in version 4 is that you can do all the configuration you did in the old client at run-time, while in version 3 you had to take a number of decisions before connecting to the remote server and, once connected, you could do very little. I'd just like to understand how the new version is more complicated compared to the old version, so that we can improve it. I'm not going to praise NoMachine if you are not comfortable with closed source software.