Britgirl

[Britgirl]

We’ve not been able to reproduce this, not with Enterprise Client nor with the free version. It could be that something changed on your system. But we are glad it’s resolved. Should the problem come back, let us know.

[Britgirl]

“though navigation with arrows is worse.”

What do you mean exactly?

[Britgirl]

Hi, are you able to send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

The best option now is to wait for developers to finish implementing full support for Sway.

[Britgirl]

The logs are clean. Are mouse clicks not actually working or is it the screen which is not updating?

In the case of the latter, it could possibly be because the host is headless. Take a look at this article which contains some useful tips.

Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973

[Britgirl]

At the moment it is not possible. We have a Feature Request already inserted into the development roadmap for the NoMachine 9 tree.

[Britgirl]

At the moment it is not possible. We have a Feature Request already inserted into the development roadmap for the NoMachine 9 tree.

[Britgirl]

If you are still experiencing the issue with NoMachine, what you can do is send us the logs from the affected Linux Mint server host. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Just an update on this, we still weren’t able to reproduce your issue, but based on the logs you submitted we reported the 2 files which were being blocked as false-positive by Trend Micro.

[Britgirl]

It’s not clear whether you made the change to the player.cfg that was requested. On the Mac you are connecting from, look for the cfg file in .nx/config in your home directory. It’s not in the path of the application.

Also confirm if you are using an external keyboard.

[Britgirl]

Hi, thanks for submitting your feedback. The connection links in the !M in the tray were present in earlier versions, preceding v7. When we released NoMachine 7 we redesigned the interface in order to make the opening of, and access to, multiple sessions faster because this is the most common use we have found amongst our users and what our users asked us for more frequently. The connection links were removed from the systray to put these recent connections in the Machines panel which can be reached in two clicks (one click on the monitor, one click on ‘Main window’). This, by the way, also allows us to declutter the !M icon: a space that we need as we move forward with our development roadmap.

[Britgirl]

Hi, I’m assuming you have the latest NoMachine packages on both sides, player and server. An issue on Mac and related to external keyboards was fixed a few releases ago.

You can read more about it here:

Some keys are not correctly mapped on a Macbook external keyboard
https://kb.nomachine.com/TR02V11091

If you are experiencing the issue on an external keyboard, the workaround is to change the following key in the player.cfg: <option key="Ignore the keyboard physical layout" value="true" />. Exit the player first, make the change, save and then reopen the player and start your connection.

[Britgirl]

NoMachine removes the public key when node/server (with nodedel/serverdel) are removed provided one can reach the other. For example, when the node is removed from the server, but that node is unreachable, the public key of the server will be left on the node host. The node will still be deleted. In the case of inverse connection, the nxserver --serverdel will connect to the server and remove the node’s public key, but if the server is unreachable when the command is run, then the public key will not be removed. The server will still be deleted. When I say “unreachable” it can mean the server/node is missing or stopped, or the connection between the two has been interrupted for whatever reason.

All connections are encrypted using SSL, you can read more about this in our detailed article about security: https://kb.nomachine.com/AR04S01121

[Britgirl]

Hi, everything works correctly in our labs and following the same steps you took. Are you sure you are not connecting to a different machine?

[Britgirl]

Good to know it’s now working.

[Author]

Posts