Forum Replies Created
-
Posts
-
Codec string: H.264 NVENC/DXVA, audio Vorbis 22kHZ stereoThis shows that NoMachine is actually using hardware decoding. Can you describe the problem you are encountering?
NoMachine Terminal Server is targeting organizations with a need for unlimited sessions and/or have a large number of users. Also consider the support that comes with a subscription as well.
For individuals/professionals or very small units, NoMachine Workstation might be a better option 😉
Thanks for letting us know anyway, I’m glad a clean reinstall fixed the problem. If it happens again, let us know.
If this is a headless Linux machine, please take a look at his article, point 3 in particular:
Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973A specific case which leads to black screen on Linux is when the X server is running but it is not rendering. In this case NoMachine doesn’t use its own virtual display because it detects that the X server running, so you need to turn back on NoMachine’s virtual display. I say “turn back on” because before the system crashed (we can’t be sure if it was the actual connection that crashed), NoMachine was running fine.
I’m glad you got the demo up and running. Which product did you choose in the end? 🙂
Out of interest, you wrote “product feature chart shows even the basic versions supporting Web access”. Can you tell me which chart you were looking at? I will make sure it’s corrected.
The comparison of NoMachine Free Edition and Enterprise Desktop is available here: https://www.nomachine.com/remote-access-for-everyone
Sorry to hear that. The article I linked included the tips and instructions on how to set key-based authentication with the NoMachine Free Edition, explaining how to add the public key to the server, so I’m not sure why it wouldn’t address your issue. It would have been useful for us to know if one of the steps was not clear or which step didn’t work for you.
We check that NoMachine works out-of-the-box with myriad distributions and an almost endless choice of desktop environments and display managers. So it would have been useful to know which distribution(s) you are using to allow us to investigate internally to make sure that there’s not something we’ve missed.
Check the Knowledge Base. It works like that because Linux works like that, a unique operating system in doing so. We include a nxagent virtual X server that you can run, just to make one X server that the system can “see”, one that can run your desktop software and one you can connect to.
The article explaining how to do it is here:
Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973Port finished. Will be released as part of the version 8, so shortly. We hope very shortly. It has been a lot of work, as you can imagine, but it will be an important release. Not only because of the M1 port.
Can you show me the output of xmodmap -pke? What does xev utility show when the problematic keys are pressed?
The logs show that this is not a NoMachine problem. In your case of the big cursor, NoMachine shows it because this is the info that is received from the OS.
Hi, we have not been able to reproduce the problem on the latest 7 version. Incidentally, the latest version of NoMachine was released after you originally submitted this topic, so I need you to confirm that you have the 7.7.4 installed on both sides. We can then send you a debug package.
Hi, it looks more of an issue related to configuration of your set-up. We’re not aware of issues with RSA keys and NX protocol. Did you take a look at this article?
How to set up key based authentication with NX protocol
https://knowledgebase.nomachine.com/AR02L00785If you’ve followed the tips there, maybe tell us the connecting client distribution and version, and then tell us what OS and version it is on the server side. It would also be useful to know what NoMachine product you’ve installed on the server side, and the version of the NoMachine software (both sides). Thanks.
Depending on the links that you followed from the tutorial, you will need with a product from the Linux Terminal Server family or the Enterprise Desktop. All these products are available as evaluation software (30-days) in the Download section of our website:
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop
https://www.nomachine.com/terminal-server (scroll down to see the details of the individual products)To download any of these, please use this link available in the website menu https://www.nomachine.com/download-enterprise
I’m assuming you restarted both computers after installing?
The error that is shown in the log you attached suggests that the Windows firewall could be blocking the NoMachine connection.
Can you make a quick test? Disable the firewall (this is just for the duration of this test!) on both of the computers and try to connect.