Forum Replies Created
-
Posts
-
Let’s concentrate on the W10 and the W11 computers to keep things simple 🙂
Please take a look at the following article and make sure you have followed the steps for enabling automatic port-mapping, https://kb.nomachine.com/AR04S01122. You can also see here https://www.nomachine.com/getting-started-with-nomachine#internet. If you are connecting over the Internet, you need to use the IP address that is facing the internet, ie. the public IP address. If it is not showing up in NoMachine, you can check it using, for example, whatismyip.com.
We are aware of the first issue and are currently investigating possible solutions.
With regards to the second issue, the default behaviour of NoMachine with regards to CAPSLOCK is that it does not interfere in any way with the physical status of CAPSLOCK of either machine. The remote side is synced to match the local client when you start typing.
This means that if your CAPSLOCK is ON on the local client, and you start the session, and on the remote server side CAPSLOCK is OFF, it does not automatically come ON on the remote side. However, if you start writing, you will get CAPS.
Similarly if you have it OFF on the local side, and CAPSLOCK is ON on the remote side. It stays ON on the remote side. However, when you start typing, remote status is synced to match the client status and there will be no CAPS.
Is what I have described does not match what you are experiencing in your set-up?
Hi,
so just to clarify, you have 3 computers on the same network (1 Win 11, 1 Win 10, and 1 other which you tried and which was working, let’s call it MachineC), and they are all on the same LAN.
The reported IP matches not only what NoMachine says is the IP, but there’s a wholly different and unrelated program that is using the same IP to share a data connection and that also matches that IP.Can you give some more details? Is this program on the Win11 machine? If you disable it, can you then connect? You won’t be able to connect to your computer if the port that NoMachine uses is in use by another application.
If you’re still not able to connect, can you confirm that they are all on the same LAN? Can they all “see” each other. With that I mean whether your Machines panel is showing the other machines on your same network (https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network). Can you see, from MachineC for example, the other two? Can you see, from your Win10, the Win11 computer?
When you connect to any of your machines, are you connecting by creating a connection manually (via the Add button), or are you connecting through local discovery? You can answer with a screenshot of the Machines panel if you prefer.
we assume you are using a stock Debian 12 in its default configuration, so we can assume that you downloaded the package to the Downloads folder. You need to specify the relative path to where the package is located. For example, this could be:
sudo dpkg -i /home/$USERNAME/Downloads/nomachine_8.16.1_1_amd64.deb
It seems that the gdebi package manager on Debian has a problem. This means that any package you try to install will not work, not just NoMachine. Installing from the command line with dpkg -i should work however.
If you still prefer the GUI method, try opening gdebi as root. It was discussed here in an external forum:
https://unix.stackexchange.com/questions/405520/gdebi-keeps-crashing-when-install-is-clicked
The changes that were made in KDE Plasma 6 were pretty significant, so adapting NoMachine to the new EGL backend of KDE has been as equally substantial. But good news, tests are now being done 🙂
Are you referring to https://kb.nomachine.com/TR05V11141? It has not yet been fixed.
Hi, the link is correct. Can you tell us the exact steps you took to install the package? Did you run in CLI:
$ sudo dpkg -i nomachine_8.16.1_1_amd64.debHave you tried unticking the box “Secure mode” and using the Network:Default option in the Ubiquiti firewall?
Hi, check in the mac’s Accessibility, Screen Recording and Full Disk Access that NoMachine and nxnode (a component of NoMachine) have been correctly added in the Privacy panel. Remove and add again if necessary. This article shows the panels to check: https://kb.nomachine.com/AR11Q01061. Restart the nxserver. Does that help?
Hi, it sounds very similar to this bug report.
Cannot login by NX protocol and private key when option ‘Import the private key to the connection file’ is checked
https://kb.nomachine.com/TR05S10271As a temporary workaround, do not check option ‘Import the private key to the connection file’ in the UI.
The latest 8.16 provides a patch for this. Please update your software.
Here is the Trouble Report documenting the issue: https://kb.nomachine.com/TR01W11266
The temporary workaround is to prevent the monitor from entering the sleep mode: open System Settings -> Lock Screen and set: ‘Turn display off when inactive’ to ‘never’. We have a patch already lined up for release and we’ve scheduled a release for this week.
Hi,
the connection windows remains white and closes in few seconds
Try disabling hardware decoding on the computer you are connecting from in the player.cfg file. To do that follow the instructions here: https://kb.nomachine.com/AR07U01202. In your case, you should choose completely disable, so option 3 (). You must quit the player first before making this change from the !M in the system tray. Then try connecting again.