Tor

[Tor]

We’ve published an update on Play Store right now, as always it’ll be available in a few hours. This version fixes a freeze occurring sometimes when the client connects to the remote desktop. Can you try it and let me know if it solves your issue?

[Tor]

Hi.

This feature will allow to configure the client to never close:

Running NoMachine client in kiosk mode
https://www.nomachine.com/FR02L02809

A quick solution with the current version can be implemented with a script that uses the option suggested by drichard:

#!/bin/bash

while true; do
  /usr/NX/bin/nxplayer --session connection.nxs --exit
done

[Tor]

Hi!
You should do nothing special, the button must be visible when you connect to a Windows OS. We solved a similar problem in an old version, can you confirm that you’re using 4.3.30 also on Windows Server 2008R2?
If the installed version is the same on client and server, it would be helpful if you could send client side logs to issues[at]nomachine[dot]com. You can find them in the directory %USERPROFILE%\.nx\

[Tor]

Hi jnko.
All 4.x versions are compatible so there must be something more. We’re investigating it. In the meanwhile if the client will crash again, could you please submit the crash report to Google by using the dialog appearing when the app closes? You may also add a little comment, so that we know that it comes from you. Thank you very much.

[Tor]

Hi mia.
We’re heavily focused on the extended keyboard functionality and we plan to include it in the next release. We’re also working on the middle mouse button, but it’s part of another feature that will require more time to be completed. If there is a gesture that we can use to quickly introduce that button press, we’ll add it for sure!

[Tor]

Hi snejok.
The upload/download items should not be visible when file transfer is disabled. Could you please send node side logs as usual? 🙂

[Tor]

But I noticed that I can’t start a virtual session when I removed nxplayer.bin. Nxplayer’s connection window shows spinning gif for 120 sec and then shows an error:

This should not happen, we’ll investigate it. Did you also try to remove the execution permissions on nxplayer.bin, or just limit them to the file owner?

[Tor]

Hi snejok.
We’ll find a way to make it more clear, even if I doubt we’ll replace the spinning wheel with a button.
Can you give me details about the connection problem? For example, if the connection is taking too much time we may show an hint explaining how to stop it.

[Tor]

Hi Igor.

Are you using a custom keyboard, or the default Android keyboard?
Those edit boxes are inside a session or do you refer to boxes of the client, like for example connection search field? At the moment we cannot reproduce the issue, any more information will help us.
Thanks!

[Tor]

Hi feroze!

Can you please report the exact versions of NoMachine on client and server? It is important to determine if we’ve fixed some of the issues you are experiencing.
About the multiple monitors on the server, we’re working on a feature that you will find useful:

Giving the possibility to switch between monitors of the remote server
https://www.nomachine.com/FR11K02797

While waiting for this feature you may have a better experience by disabling the scaling mode. You can do it by unchecking the button ‘Fit to window‘ in the Display menu panel.

[Tor]

Hi dahoui.

There have been changes in the file system on Yosemite that may affect also the position of the core fonts shipped within XQuartz.
Please confirm that on your Mac the directory /opt/X11 exists while /usr/X11 is missing. In such a case, you can create a symbolic link to work around the issue by executing the following command in a Terminal:

sudo ln -s /opt/X11 /usr/X11

We’re going to open a Trouble Report and release a fix soon.

[Tor]

Hi heywood.

When the client starts the first time, it selects a free port in a range defined in settings and tries to always use the same, in order to ease the firewall configuration and match the UDP rules.
When there are multiple instances running, each client using UDP selects a new port in the range instead of the “default” port. You can change both the default port and the range in Edit => Advanced => UDP settings (visible only if NX protocol is selected).

You should only need to configure your router to open the range of selected ports.

[Tor]

Yes, it is correct, the ‘–exit’ closes the player as soon as the connection stops or the session gets disconnected. In the other cases, the player goes back to the list of connections or to the Edit dialog (the latter in case of ‘–session’ option).

[Tor]

Hi snejok. 🙂
You can find a description of the feature and a list of supported shortcuts here: https://www.nomachine.com/FR04L02812

Each shortcut can be reconfigured or disabled, so you can decide which keys combination better fits your need and most of all avoid clashes with shortcuts existing in the local or remote Operating System.

[Tor]

No problem. 🙂 The closure is normal since it is how the ‘–exit’ option works. We’ll add a description in the help to explain what the user can expect when using it.

[Author]

Posts