Forum Replies Created
-
Posts
-
Totally agree. Which is why in version 9 it is possible to use a host certificate and key issued by Certificate Authority. Provided you have NoMachine 9 installed, the client will verify whether the issuer of the certificate is a trusted certificate authority, whether the certificate has expired and whether the certificate has been revoked.
We’re just in the process of creating an article which I will provide the link for once it goes public. I wanted to respond to make clear that NoMachine 9 does support CA certificates.
Hi,
see the tips here https://forum.nomachine.com/topic/user-for-instant-access#post-52574 and here https://kb.nomachine.com/AR03S01118. Go to the section for Windows, just below figure 2.
I’ll post here for convenience
1) User Principal Name: <username>@<domain> – so you can use this. If you are not able to, please tell us what error you are seeing when trying to promoted to authenticate on the target Windows machine
2) Down-Level Logon Name: <domain>\<username>
3) Short format name, just ‘username’, domain is implicit.
This is not really a different format, since it is just the Down-Level Logon Name without the domain part.Hi, can you gather the logs with debug enabled? Please follow the instructions in this document: https://kb.nomachine.com/DT07S00243. It’s valid for v9 as well. Reboot the server, or logout and log back in. Gather logs again. Thanks!
This problem should not exist. We also (re)tested it and cannot reproduce. Can you be more specific, tell what application you tried to start, what error you got, what you see in the logs?
Hi, can you tell us the exact distribution and desktop environment on that Linux machine. What NoMachine version did you uninstall?
Can you check permissions are set correcting in the macOS system setting? (System Settings -> Privacy & Security -> Accessibility)
Also tell us if the server is headless.
Logs of the server machine would be useful. Please follow the instructions here: https://kb.nomachine.com/DT08U00298#1.1. You can submit them here or send directly to forum[at]nomachine[dot]com. Make sure to use the topic link or title as the subject of your email. Thanks!
That behaviour is directly related to the Docker Desktop application. It was created to work on physical desktop. When you create a virtual desktop and start Docker Desktop it will start on the physical desktop. The same behavior appears on vnc and rdp sessions as far as we are aware.
Can you first try disabling hardware encoding on the server-side? Go to server settings -> server performance -> uncheck “Use hardware encoding”, then connect.
If that doesn’t help, try disabling HW decoding on the client side and then connect. To do that, open the NoMachine menu panel inside the session by Ctrl+Alt+0 or click on the page peel at the top right corner of the window. Then click on Display -> Change settings. In that panel click on the Modify button to open the advanced display settings. Click on ‘Disable client side hardware decoding’ to disable it.
Do either of those help?
Please update to the latest version, NoMachine 9 includes the fix.
Here is the link to the Trouble Report: https://www.nomachine.com/TR03W11302
NoMachine Network will use whatever is the route set in your network, to reach the remote end-point, to reach the IP. It will use hole-punching and the other methods only if the IP is unreachable, by the standard means, So, in other words, no need “to prioritize the routing” “to go over the tailscale mesh”. But I’d like to understand what you mean with “surrender your keys”. NoMachine Network does not “hand over” any cryptographic information, needed to establish the connection. NoMachine Network works only at the “IP level”, all the usual cryptographic security remains in place as it was designed.
Hi, can you do a complete reinstall? Download from this link to the free version:
https://download.nomachine.com/download/9.0/Windows/nomachine_9.0.188_11_x64.exe (64-bit)
https://download.nomachine.com/download/9.0/Windows/nomachine_9.0.188_11_x86.exe (32-bit)