Forum Replies Created
-
Posts
-
NoMachine does not interfere with other applications as far as our tests show in our labs. You could try with a simple SSH -X started from a Linux terminal and see if you get the same behaviour. If the cause were NoMachine, there will be the same issue, but as I mentioned, our tests don’t show any similar behaviour. It seems more of a problem of the application or your other ssh server/client product. Another way to check is by stopping the nxserver completely (settings -> server -> status -> shutdown).
Can you send them to us and we’ll take a look? 🙂 Send them to forum[at]nomachine[dot]com. Zip up the entire var folder from the Windows 11 machine, we can start from that.
Then we’ll give you some further instructions.
With Tunnel mode, the client traffic is relayed through the Cloud Server with the protocol specified for the server-to-node communication. The tunnel is through server to server communication protected by OpenSSL TLS/SSL (which uses ‘ECDHE-RSA-AES128-GCM-SHA256’ as the default cipher suite, TLS 1.2 so it’s not possible to snoop the data being transmitted through the connection.
Further reading:
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.
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!
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/AR03P00973At the moment it is not possible. We have a Feature Request already inserted into the development roadmap for the NoMachine 9 tree.
At the moment it is not possible. We have a Feature Request already inserted into the development roadmap for the NoMachine 9 tree.
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!
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.
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.
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.
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/TR02V11091If 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.