Forum Replies Created
-
Posts
-
Q1- Where can I find the fingerprint on the server to check it ?
openssl x509 -noout -sha256 -inform pem -fingerprint -in /usr/NX/etc/keys/host/nx_host_rsa_key.crt
Q2- Could you confirm all is OK with this manual procedure ?
Yes, it is a standard procedure to pre-configure client’s hosts.
Understood. The name given there is actually the name of the session file. In the current version, the name of the connection is displayed in the caption instead of the hostname or the name of the node. This is the standard default behaviour across all products. To distinguish among the nodes you could create one connection for each node, give it the node name and save it. Be sure to check the ‘Save the selected node in the connection file’ option.
For a future version we already have planned the possibility to add the option to display the node name in the client window caption with Cloud Server set-ups. On the basis of your requirements, should it be optional or should it be the default standard?
The caption could be something similar to this:
<session name> (<node name>) - NoMachine <session name> (<node name> via <CS name>) - NoMachine (for multi-level only, show node parent name)I imagine this would this satisfy your requirement, but if you have another idea, by all means we will be happy to evaluate your suggestion.
NoMachine is not a password manager. Stored credentials are scrambled and you can read more about this in the following article: https://kb.nomachine.com/AR01C00125
maxim-nomachine, can you send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
The -head and -tail extracts were useful. What we see is that all the networking resources (such as socket handles) get an error at the same time. Can you check whether there are any antivirus, anti-malware, security system that may be interfering? When the problem occurs, the NoMachine Player process remains in the background instead of closing (so it continues to log, hence the big logs, both nx session and the log node session logs show the same thing by the way and we’ll see what improvements can be made to mitigate this). It should be easy to understand whether disabling the “security system” or adding NoMachine Player among the exceptions helps.
You wrote:
added the pubkey to the “authorized.crt” file in %USERPROFILE%/.nx on the host Windows machine
it should be .nx/config. Maybe this is the problem? Can you follow the instructions for How to set up key based authentication with NX protocol in this article https://kb.nomachine.com/AR02L00785?
Is it possible there is some trivial error like a typo in the file name, or even wrong permission?
You can also send us the logs from both player and server machines. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
So the steps to follow to “unlock” the ctrl key are the same and we can therefore establish that it’s the same bug. I am unable to provide you with a target release for the fix at this time, but please use that link to the Trouble Report to monitor its status,
I have uninstalled them all, by using right click in the application in directory and “Move to Bin”. But I don’t know if there are any left over bits that might be causing issues.
You need to make sure you have uninstalled the other components correctly. For example, the correct way to uninstall USB Network Gate you should follow the instructions here: https://help.electronic.us/support/solutions/articles/44001312963-usb-network-gate-uninstallation-on-mac#:~:text=To%20completely%20uninstall%20USB%20Network%20Gate%20and%20all,but%20not%20uninstall%20the%20daemon%20and%20drivers%20J
Do not uninstall by moving USB Network Gate.app into the Trash, as this will only remove the GUI, but not uninstall the daemon and drivers (from their website).
So install UNG again, then uninstall the right way following those steps.
To compile nxusb kernel module you have to delete line 1198:
".owner = THIS_MODULE," in "/usr/NX/share/src/nxusb/nxusb-vhci-iocifc.c"and then runsudo makein the same directory as that file.What NoMachine message are you seeing when you connect?
Did you already take a look at the guide here?
https://kb.nomachine.com/AR04S01122 ?Any idea why the flatpak version couldn’t install?
We cannot know. We are not responsible for NoMachine packages that are in repositories which we don’t have strict control of or don’t officially support. That’s why I wrote to always download and use the packages from the NoMachine website.