Forum Replies Created
-
Posts
-
The fact you also can’t connect with other protocols SCP and SSH suggests a problem on your Windows machine and not on the NoMachine server. It would be useful to see the full logs to understand if the Windows machine is actually connecting to the correct server.
The hosts.crt stores the fingerprints of known hosts, as received from the server hosts themselves. If a different fingerprint is found, or the fingerprint has changed again, it means that you are possibly not connecting to the server you expect, but to another. Tracert can be useful to trace the network traffic routing.
You can find information about how and where NoMachine keys, certificates and fingerprints work in the following documentation:
https://kb.nomachine.com/AR10K00729
How to verify the NoMachine server host fingerprint informationhttps://kb.nomachine.com/DT07S00229
Section 1. Keys and CertificatesHi, the PIN is not accepted when connecting to the desktop remotely. You must use the password that you set up during the creation of your account. See more about this here: https://kb.nomachine.com/AR03S01118, quoting what is written there:
Windows supports the following formats for the account names. They can all be used to log-in by NoMachine:
1) User Principal Name: username@domain
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.Ref. https://docs.microsoft.com/en-us/windows/win32/secauthn/user-name-formats
In addition to formats above, there is also the possibility to associate a ‘friendly name’ or nickname to the account. The friendly name, which corresponds to the ‘Full name’ in the account settings, can’t be used to log-in by NoMachine. You need to use instead the name of the account, which is unique and corresponds to the ‘Username’ field in the account settings.
No such option exists I’m afraid. Can you tell us what you would like to achieve? It might be possible to do it in some other way?
Is there an application maybe grabbing the cursor. You could try installing
xdotooland run the commandxdotool key XF86Ungrabwhen the problem occurs, to verify if the cursor works correctly. If it does work correctly, it means another application is grabbing the cursor.
It is a combination of 2 issues. One is documented here, https://kb.nomachine.com/TR05V11141, which causes the default capture method (EGL) to fail. The second issue occurs when using the fallback method (DRM) and it is due to an unexpected colorspace format which we’re still investigating and will keep you posted.
It could be the already known issue here: https://kb.nomachine.com/TR05V11141. But we would like to check to make sure. Are you able to send us the logs from the server machine? 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!
how about the username? You mentioned the error message is translated. Is it possible you are using non-latin characters in the username? We can check the logs to see what is causing the authentication error, they will show whether it’s a wrong username issue or something else.
You should enable logs on the Linux server following the instructions here, https://kb.nomachine.com/DT07S00243, and then on the Mac client, the instructions are in the 4th step of that document. The client logs should be retrieved when the player showing the authentication error is open, so after reproducing the problem, do not close the player. Send everything to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
It looks like a wrong password caused by keyboard layout mismatch. What is the message you are seeing?
Check your FW setting:
sudo firewall-cmd --get-default-zoneIf it returns “public” – this maybe the problem. The workaround is to change the zone or adding a different range. If you want to continue using “public” zone, then do the following:
sudo firewall-cmd --zone=public --add-port=1025-65535/udp --permanent sudo firewall-cmd --reload sudo /etc/NX/nxserver --upnpmapAbout the cursor issue and black screen, we need logs in order to understand why that is happening. Send us full logs (from both sides) 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!
I don’t have ufw (as far as I know it’s ubuntu’s firewall)
Sorry my bad.
Disable any FW you have (temporarily) and try again.
Alternatively, you could try port-forwarding
How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122Hi, it could be a firewall issue. We have observed similar behaviour when after enabling ufw firewall, UPnP port mapping is not working.
In that case you can allow incoming UPnP traffic from your router by executing the following command:
sudo ufw allow from 192.168.1.1 port 1900 to any proto udp(where 192.168.1.1 is a router address). After allowing this traffic, you can initiate UPnP mapping by running:
sudo /etc/NX/nxserver --upnpmapOnce done, UPnP should be operational on your machine. Remember to repeat this process on every machine where UPnP functionality is required.
Note: To find your router’s IP address, you can use the following command:
#ip route | grep default
If you’re using any additional outer firewalls, ensure to add a similar firewall rule to allow UPnP traffic as mentioned above.
Hi,
we’ve reproduced the same behaviour and a fix is already scheduled in the next release. You can track the fix using the following link:
Frozen screen on macOS15 after display goes to sleep
https://kb.nomachine.com/TR10V11230Tamer, the file nx-sourceenv.sh is created by 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!
What Linux distribution and version is installed on the server?
What desktop environment and version are you using?
Are you aware of any security policy which is set on that machine?Ok, thanks for the additional info. We confirm that the issue is https://kb.nomachine.com/TR05V11141, which developers are currently working to resolve.