Britgirl

[Britgirl]

There are a couple of similar topics in the forum about this already, one of which is:

Clipboard between Mac and Ubuntu rarely works

This is a problem related with how Gnome works. SuperKey, which on macOS is mapped to Cmd key, is a special key which works with high priority. You should enable activegrab as described in that link to the post above.

The article here provides the full explanation and workaround:

How to send ‘Option+Click’ from Linux to macOS
https://kb.nomachine.com/AR10Q01058

 

[Britgirl]

It will indeed be “Free to add any machine that you want to reach” (as per the web page).

“Everybody will be able to add their own machines to Network for free and without needing a Network subscription. Access to NoMachine Network will be free for everybody. It will also be used for two-factor authentication, something we’re going to introduce together with Network.”

And that still stands 🙂  So, free to publish your NoMachine-enabled computers on Network (including computers where the free edition is installed) and you won’t need an account to publish them on Network; free to use the 2FA service provided you have an account, free to login with your account to the Network service in the GUI (from version 9 onwards) and see these computers you published, if you want.

But, connecting using the Network service to your computer, any computer, published on NoMachine Network will require a subscription. You won’t need a subscription to register, you won’t need a subscription to use 2FA, you won’t need a subscription to log in with your account, you’ll just need a subscription when you want to connect over Network. For pricing, you should contact our Sales Department.

Of course, Network is optional. Users can continue to connect to their NoMachine computer using the traditional IP address exactly as they do now.

[Britgirl]

Quoting from the page: Any user that wants to access a computer via NoMachine Network will pay a monthly fee, regardless of the number of machines they want to access, through a NoMachine Network subscription.”

You will be able to combine the free edition of NoMachine (free to download, install and use) with NoMachine Network (as well the commercial Enterprise products). To connect to a “NoMachine computer” using the Network service, a Network Subscription will be required.

 

[Britgirl]

Our upcoming NoMachine Network will let you achieve this. It’s coming with version 9 which is near completion. You can read more about this here on the following web page: https://www.nomachine.com/network

[Britgirl]

Development of the feature you are interested in will start after we release version 9, so whilst it’s possible that it will be in one of the releases of the v9 branch, we are not able to give you an ETA at the moment. We’ve taken note of your interest, so if we have pre-release packages for you to try out, we’ll be in touch 🙂

[Britgirl]

Indeed NoMachine’s built-in 2FA will be in version 9. We are late with delivering NoMachine 9, we know, but it’s coming 🙂

To use your own 2FA, you need to first enable 2FA in PAM.

1) open a terminal on the Mac server side
2) make a back up sudo cp /etc/pam.d/nx /etc/pam.d/nx-ori
3) then run sudo cp /etc/pam.d/sshd /etc/pam.d/nx (to enable 2fa in PAM)
4) start a NoMachine connection (no need to set anything in the Edit – Authentication section of your connection)
5) you will then be prompted for the password and code.

Let us know how you get on.

[Britgirl]

It could be a problem with your permissions. Take a look at this topic https://forum.nomachine.com/topic/authentication-failed-with-error-7.

[Britgirl]

Our own 2FA functionality will be made available with the next major release, version 9. Can I ask what authentication app you are using?

[Britgirl]

Hi, what is the Linux distribution you are using on the Linux server and what is the desktop environment? Is this a headless Linux server or do you have a monitor attached?

[Britgirl]

If it happens again, check to see which sound server is being used on the server host?

Please open /usr/NX/etc/node.cfg on the server host and check which value is set for the AudioInterface key. If they are different, set AudioInterface to the appropriate sound server.

For example, if “AudioInterface pipewire” is set in server.cfg but the sound server
is PulseAudio, set the key to: “AudioInterface pulseaudio” .

Then create a new session. If this doesn’t help, we will need the logs as I suggested before.

[Britgirl]

This is a copy of https://forum.nomachine.com/topic/ctrl-cmd-key-mapping-doesnt-work-from-linux-to-mac.

[Britgirl]

Hello, I understand that you would like each of your users to connect to their own Windows desktop. NoMachine lets multiple users connect to the same Windows desktop (desktop sharing), so the users will be viewing and interacting with the same desktop. If you want each user to have their own desktop environment, you will need to create ‘n’ number of virtual desktops running Windows, each one for one user.

Permitting multiple desktop environments to run on the same OS is a feature available in the Terminal Server for Linux family. These products permit multiple “virtual desktop sessions” on the same host. Each virtual desktop is separate from the others, allowing users which connect to work within their own (Linux) desktop environment.

More information is available in the following articles in the KB:

Does NoMachine for Windows allow multiple users to connect to their own individual desktop on Windows?
https://kb.nomachine.com/AR10Q01052

What is the difference between physical desktop connection and virtual desktop connection?
https://kb.nomachine.com/AR10K00700

[Britgirl]

Hi, what you can do is install the packages for 64-bit, there is no need to install any additional library.

[Britgirl]

Hi, if I understand what you wrote, I think that running the “nxserver --debug --enable all” and then sound came back was just a coincidence. If you have problems with sound again within the NoMachine session (from Windows to Linux), submit logs from the server.

[Britgirl]

Hi everyone,

There are two issues with the current implementation of NoMachine on RPi5.

Just so it’s clear what the situation is. The problem with RPi5 (not NoMachine) is that it lacks the capabilities of a full GUI (raspi-config app), so installing has to be done via the command line. This applies to any application you want to install, including, of course NoMachine. You can try installing with another graphical package manager.

Secondly, the RPi5 has a small identity problem 🙂  If you run ‘uname -m’ to know what architecture it is, you get ‘aarch64’ as the output.  But there are 32-bit libraries installed there:

file /bin/cat/bin/cat: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=ae08710495f166403a0b241bb0601fe595494e59, for GNU/Linux 3.2.0, stripped

so you would need to install this:
https://downloads.nomachine.com/download/?id=104&distro=Raspberry&hw=Pi4

or this:
https://downloads.nomachine.com/download/?id=109&distro=Raspberry&hw=Pi4

Now to NoMachine – as I’ve mentioned before, there is a Trouble Report (see my post from earlier in the thread) which is related to the Wayland compositor. The workaround, which is temporary whilst our developers fix it, is to disable Wayland and use X.org.

RaspberryPi OS:
sudo raspi-config
Advanced Options -> Wayland -> X11 -> OK -> Finish -> Yes (to reboot)

[Author]

Posts