Forum Replies Created
-
Posts
-
I don’t think elevating the severity will change the fact that the solution is to encode monitors in separate video streams due to the video encoders not supporting such high resolutions themselves. As Fra81 mentioned it’s a rather big task and one that is underway. Believe me, if there had been a quick fix, we would have already pointed it out in the TR 😉
Here is the Trouble Report for this bug: https://www.nomachine.com/TR04O07712
Please sign up to the ‘notify me’ tool to know when a fix has been released.
If you have NoMachine virtual desktop sessions running you can do (via ssh):
sudo /etc/NX/nxserver --history | grep Connected sudo /etc/NX/nxserver --terminate <session ID>(We’re currently evaluating simpler nxserver commands).
Otherwise, a simple restart via ssh.
I’ll get the notify me checked. It’s weird because I received notification that you had updated this topic.
We’ll need to see the logs from both sides. Please follow the instructions you can find here: https://www.nomachine.com/DT07M00098
Then, zip them up and attach them to an email which you can send to forum[at]nomachine[dot]com
If you are installing NoMachine in a VM instance, please refer to https://www.nomachine.com/AR11E00489
“…for every virtual server instance of VMware that you wish to connect to, one subscription license file will be required. So if you have a server machine that will be providing 4 virtual instances by VMware, you will need 4 x NoMachine, or alternatively 4 X any of the Enterprise or Terminal Server subscriptions depending on your needs.”
Or have I misunderstood?
Hello,
thanks for the update. This would appear to be a licensed version with technical assistance enabled. Next time it might be better to contact your administrator and ask them to open a support ticket so that the team can investigate according to your entitlements 😉
Please make sure your Windows installation is up-to-date with any recent software updates. Also, use the latest NoMachine version. Then let us know if you continue to have the same issue.
Hi, we’ve reopened the Trouble Report. Please sign up to the notify me tool to know when a fix has been released. Thanks for reporting.
As I’ve just mentioned, we’ll need to send you a debug version because 1) the logs didn’t show anything useful and 2) we haven’t been able to reproduce the problem despite our tests since you submitted the logs. I take it that you have updated to our latest release?
Apologies for the delay in getting back to you. Developers have been busy with the recent release of 5.2.21. Logs didn’t show anything useful, so we will need to send you a debug package. Can you confirm if it’s 32 or 64bit please. The debug package we send you will be for the latest version assuming the bug is still present.
@NetForce, we got both sets of logs. Thanks! If we need to send you a debug package for the Ubuntu side, can you tell us whether it’s 32 or 64bit please?
We’ve inserted a new TR to track this bug. Please sign up to the ‘notify me’ tool to know when a fix is available.