Forum Replies Created
-
Posts
-
Hi, please let us know if you are still experiencing the black screen issue when connecting from Ubuntu. Update to 8.16 on both client and server. If you are still able to reproduce the issue, disable HW decoding on the client side. To do that, please follow the instructions here: https://kb.nomachine.com/AR07U01202. In your case, you should be disabling by setting <option key=”Enable hardware accelerated decoding” value=”disabled” />
The unsupported file message is because you missed off the .deb at the end 🙂 If you want to install the NoMachine package for Debian that you downloaded from our website, it should be
nomachine_8.16.1_1_amd64.deb.If you are a Linux newbie, it might be good to look at this web page here which explains how to use the dpkg command
https://www.digitalocean.com/community/tutorials/dpkg-command-in-linux and here about apt https://www.digitalocean.com/community/tutorials/what-is-apt, https://www.digitalocean.com/community/tutorials/package-management-basics-apt-yum-dnf-pkg. Another useful link for beginners is here: https://kifarunix.com/install-nomachine-on-debian-12/#install-no-machine.whichever install command you choose it’s
$ sudo dpkg -i nomachine_8.16.1_1_amd64.debor
$ sudo apt install ./nomachine_8.16.1_1_amd64.debAlternatively, still in the terminal, run
sudo gdebi-gtk. This opens gdebi GUI as root which should work according to the external link I pointed you to in an earlier post. Then select File->Open->’Choose nomachine_8.16.1_1_amd64.deb’.Hi, we categorized it as minor because, whilst it is compatible with Chromebook notebooks, the NoMachine mobile app is designed to be used mainly with a touch interface. The solution is not as simple as it seems because of the way Chromebook sends that event to the application which makes it hard to be converted to a scroll for the remote desktop.
I can’t be the only Chromebook user – what do other people do?
The alternative is to install the Linux desktop version of NoMachine in a Linux VM on your Chromebook.
The next major update for mobile, NoMachine 9, concentrates on integration with the upcoming NoMachine Network service and 2FA. After then developers will be able to concentrate on fixes for known issues in successive updates for the app.
For installation, you can follow the tutorial here, it shows the free edition as the example, but the steps for installing Enterprise Desktop are exactly the same! Once installed, it’s ready for use. Default configurations match most scenarios.
https://www.nomachine.com/getting-started-with-nomachine
Then, if you want to know a bit more about configuration, take a look at the guide here: https://kb.nomachine.com/DT07S00246.
And if you have further questions, let us know 🙂
Thanks for the further suggestions. As you said, Linux CNC is plain old Debian 12. Also consider that NoMachine installs on pretty much most Linux distros without much ado, including Debian 12. If it’s only the NoMachine package which is affected, ie. other applications which have been downloaded and installed without problems, we can investigate further. If not, as I already suggested, the Linux CNC forums could help with installing and configuring Linux CNC. Some of the other points you mentioned about Linux CNC would be more appropriate in the Linux CNC forums. The NoMachine forums are here for users to ask about NoMachine software, get technical assistance for NoMachine and discuss why you should be using it 😉
Hi, on the target macOS system that you want to connect to, what you need is the Enterprise Desktop package.
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop
It lets unlimited users connect to the same physical desktop at the same time. Here you can compare the free edition to the Enterprise Desktop product: https://www.nomachine.com/remote-access-for-everybody. On devices of the users who need to connect, install the free edition or the Enterprise Client (the former contains both the client and server components, the latter does not contain the server component).
Hi, are you connecting to mDNS discovered machines (NoMachine computers on LAN)? Or are you connecting to computers by creating a connection manually (i.e you insert the IP address when you create the connection).
Are other connection preferences being ignored as well, such as user credentials not being store or a custom resize mode?
How do you disconnect the session?
Hi, there is a Trouble Report open for a similar issue and a temporary workaround is available. Check the link here:
https://kb.nomachine.com/TR10U11031.It should be more or less the same. We don’t test specifically on Linux CNC, but it’s Debian-based, which we test frequently.
As I wrote earlier,
sudo dpkg -i /path_to_the_file/filename.debshould work. If it’s still not working, provide us the output of this:ls -l /path_to_the_file/file.deb
Remember, you can still use the workaround I provided earlier for gdebi. Open gdebi as root and then open the NoMachine file. Or use other workaround from link with gdebi report in the link I pasted earlier. So for example, edit as root:
/usr/share/applications/gdebi.desktopreplace:
exec=gdebi-gtk %f
with:
exec=sh -c "gdebi-gtk %f"and after that start the installation procedure again. If you try with another app that you’ve downloaded on to your machine, and you’re getting the same result, perhaps the Linux CNC forums can help as well?
Good to know it’s now working. In version 8, port mapping is disabled by default. Can you tell me what version you had installed before you updated? I.e did you have a version 7 installed and functioning for outside access?
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 a similar behaviour with regards to 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