Forum Replies Created
-
Posts
-
We have opened a Trouble Report, and you can use the following link to track its status, https://kb.nomachine.com/TR01X11700.
We have opened a Trouble Report, and you can use the following link to track its status, https://kb.nomachine.com/TR01X11700.
Hi,
audio streaming can be disabled in the Audio settings panel of the session menu.
To reduce bandwidth further, you could try the following:
i) set the lowest quality in the Display quality slider in the Display settings panel of the session menu
ii) resize the remote screen to a low resolution
iii) edit the node.cfg on the server host to set ‘DisplayServerVideoFrameRate 1’ and ‘DisplayServerUseVideoFrameRate 1’
Let us know if that helps 🙂
Hi, we’re not able to reproduce similar behaviour on the latest release. You could try disabling hardware decoding on the Windows client to start off with. Instructions are here: https://kb.nomachine.com/AR07U01202.
If that doesn’t help can you send us the logs of the NoMachine server? Please set log level to debug, restart and then reproduce. Full instructions are here: https://kb.nomachine.com/DT08U00298. Send them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email.
We can send you a link to a v8 package (can you remember which specific version? otherwise we’ll send the most recent one). That way you can verify that the problem is not there. In that case, we would appreciate logs from the v8 server as well, so we can compare. Thank you!
Hello, this looks similar to a Trouble Report already open, please take a look at the link here: https://kb.nomachine.com/TR01X11699. We can send you a test version with a possible fix implemented. Would you be willing to try it?
Hi,
the Enterprise Desktop product you installed, like all products in the Enterprise suite, is available as an evaluation version for a period of 30 days. The message you see simply means that your evaluation subscription is expired.
If you want to continue using NoMachine software for free, you can still uninstall the Enterprise Desktop package, and install the free edition on the machine you want to reach. Using it is completely free and does not require a server-side subscription.
https://download.nomachine.com/everybody/
You can compare the two products at the following link: https://www.nomachine.com/everybody/nomachine-for-your-os
We are investigating. Thanks for the additional information about v8 working well. Are you able to submit those logs to us anyway? They would be useful to us because so far we’ve been unable to reproduce the problem. Please enable debug (level 9) on the NoMachine server host, restart, then reproduce the issue. Also, you mentioned earlier that you install roles and features, can you give us some more information about that? Are you using default roles or are you creating user permission groups and adding some users automatically there?Â
Hi,
send the logs to forum[at]nomachine[dot]com. Use the title of your topic as the subject of your email. Thanks 🙂Hi, from what you write and show, it looks like the root window resized, but the desktop ignored it. Can you try enabling the button “Resize remote display” in the Display menu (in the session, Ctrl-Alt-0, Display)? Does that help?
If that doesn’t help, please tell us the server OS and version. Also the NoMachine product you have installed on the server side.
Hi, yes we got them. We’ll come back to you soon. Was the workaround in the topic that I linked earlier not effective?
We’d like to send you a debug package which will allow us to extract more detailed logs. If you’re interested, let us know and we’ll send you further instructions.
No. With Filevault enabled, you have encrypted your disk which means that to allow NoMachine to connect to the screen there, it has to be decrypted first. Indeed, the macOS dialog for the password to de/encrypt the disk looks very similar to the login screen.
Are you using Cosmic? This could be related to https://forum.nomachine.com/topic/pop_os-24-04-cosmic-desktop-white-screen. So please try the workaround indicated there.
Additionally, we would need to see the full logs from the PopOS host so that we can confirm what’s causing the error. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!