Forum Replies Created
-
Posts
-
Hi, if you are referring to whether you can use the host certificate for different protocols, then yes, it’s also possible to use the same certificate with all of them.
Hi lmvdr, we have not received any email requesting the debug version. But not to worry, your comment is enough as proof. Thanks for confirming, the package is being prepared.
Please update to NoMachine 9, a fix was released for the issue you reported when using the external keyboard.
Hardware keyboard stops working on iOS after opening session menu
https://kb.nomachine.com/TR03W11295Please start a new thread if you continue to have issues.
Firstly we recommend to update your client 7 because you are using an unsupported version. If possible also update to the latest 8.17, or version 9. Logs would be useful to investigate further. A similar topic was handled here: https://forum.nomachine.com/topic/blurry-coloured-font-on-version-7-6-2.
We don’t offer a service monitoring because there is specialized software to do that. We could possibly evaluate doing something in future, but we don’t have any short term plan. Something that is not strictly related with what you asked for, but that can still be useful, is a new “Machine info” context menu entry in the machines roster that connects to the server and gets the statistics. This will be available in one of the 9.x maintenances.
Hi,
1) screen blanking is still not available with KDE due to missing support in the D-Bus API
2) it’s not possible to show a login screen because NoMachine shows exactly what is shown on the physical display, while RDP creates a virtual desktop (virtual desktops are available also with NoMachine in the Terminal Server products). One possible way to regain access to the local system is logging in from a different player (even from a phone) and disconnecting the current connection.
Hi, have you activated scaling in the Window’s own system settings?
Open the session menu (Ctrl-Alt-0) and increase the Display quality. Does that help?
If not, try disabling hardware encoding on the target Windows computer, and then also hardware decoding on the Mac.
To disable HW encoding on the Windows machine, open the NoMachine Settings there, go to Server > Performance > and make sure the option “Disable hardware encoding” (https://kb.nomachine.com/DT05U00288#3.7) is enabled.
To disable decoding on the Mac, during the session open the session Menu > Display > Change settings > Modify and select “Disable client side hardware decoding”.
As promised, here is the article
How to use custom host certificates with NoMachine v9 (Host, Client, and CRL Configuration)
https://kb.nomachine.com/AR06W01292Totally 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?