Forum Replies Created
-
Posts
-
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? We suppose Plasma but we need you to confirm.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.
Enzo5,
please refer to this article about:
How to connect to Windows with NoMachine and an empty password
https://kb.nomachine.com/AR05L00802As I wrote here: https://forum.nomachine.com/topic/windows-credentials-with-autologin#post-50897 is an easier way to get around not having a password, rather than reconfiguring Windows policies.
It certainly is not abandoned, we have had other priorities, mainly NoMachine Network, for NoMachine 9. Developers are currently working on HiDPI support, so that NoMachine can capture the screen of the server at native pixel resolution on such displays.
A note about the links you mention, you should see a page informing you that our road map is no longer in the public domain when you click on a feature request link.
Hi, I was just about to write to you for the logs and then found that you had replied with a workaround. Did you switch to Wayland on the client side or on the server side?
Would you be willing to help us debug? It would mean temporarily reverting to X11 and sending us the logs.
From the server machine, please follow the instructions here: https://kb.nomachine.com/DT07S00243
From the side you are connecting from:
– launch the NoMachine UI on the user’s computer from Programs or Menu
– click on Settings -> Player -> Security
– check Don’t delete log files on exit option
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.Hi, thanks for the additional information. We confirm what we said before. Use this link to monitor the bugfix, https://kb.nomachine.com/TR05V11141. For the time being use x.org rather than Wayland.
Hi, we need the complete logs. Please follow the instructions in the guide here which explains how to gather the right logs for debugging: 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!