Forum Replies Created
-
Posts
-
The Trouble Report is available here: https://www.nomachine.com/TR01O07470
Please sign up to the ‘notify me’ tool to know when a fix has been made available.
Thanks for reporting. We’ve reproduced it and opened a Trouble Report: https://www.nomachine.com/TR01O07476
Please use the ‘notify me’ check box to know when it has been fixed.
Fail2ban support is on our roadmap. You can view the Feature Request here:
I don’t understand what you mean? Are you talking about multi-monitors? Can you describe what you’d like to achieve with more details?
If you want to start from the first pane (see attachment tutorial_3.jpg), you can write nx://11.111.111.11:22222 and click ‘Connect’.
What happens? Do you connect?
If, on the other hand, you are using the connection wizard to create your connection (see attachment tutorial_13.jpg) you must write the hostname and then in the box next to it, you write the port number eg: Host is 11.111.111.11, so you enter 11.111.111.11. Port is 22222, so you enter 22222.
What happens? Do you connect?
These images are available in the tutorial here: https://www.nomachine.com/getting-started-with-nomachine#internet
Attachments:
You wrote that disabling hardware acceleration (decoding) on the client, the performance improves. It would seem that the HW is to blame, not really NoMachine.
You could try using H.264 software encoding, you can follow the instructions here: https://www.nomachine.com/AR10K00706. This should help diminish the use of the CPU.
In its current design NoMachine sends the content of all the remote monitors even though you may be viewing the content of one of the displays only client-side. This is to ensure a smoother experience in visualizing the content when you’re switching among monitors.
This behaviour is becoming less convenient nowadays what with monitor resolutions getting larger. We are already working on improving how NoMachine handles the encoding of multi-monitors, so that each monitor is encoded separately and content is transmitted separately to the client.
Other ways that you could further improve CPU usage is by disabling “client side image post-processing”. This applies a filter to improve the quality of the image, but consumes more CPU. This is one feature which I am sure other remote access products don’t have.
This is exactly what you can do with NoMachine, not just remote Linux machines, but Windows and Mac. You don’t need any additional software from us.
What NoMachine version and product have you installed on the connecting device? What NoMachine version and product have you installed on the server side?
What is the Linux distribution and version?
Did you get a chance to pull the logs because we didn’t receive them.
If not, I suggest you update to the latest release (5.1.62) and let us know if the problem is still being encountered. In that case, we will still need the logs 😉
We sent the package a while back and didn’t hear any further news. This topic will be closed. Make sure you update the software to the latest version. Any problems, please open a new topic.
Please submit the logs. We’ve not been able to reproduce this issue so in order to investigate we would need further information as requested by nars in previous replies.
For logs: https://www.nomachine.com/DT07M00098
Thanks for letting us know it was a configuration issue. I’ve added some tags to the forum post so others can find it.
