Britgirl

[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)

[Britgirl]

On the server side, for example with Cloud Server (and then adding your node machines such as Enterprise Desktop or Workstation hosts) as your users’ single entry point, you disable direct access to node and configure the Cloud Server to allow specific access for specific users.

You can also use custom scripts which are run on the server upon a given event. I’m not sure what server product you are using, but all the guides in the documents section have a chapter about custom scripts (Server Automation Interface).

Alternatively, you could block specific client-side IP addresses on the corporate firewall and allow only those that you want to come through.

[Britgirl]

It seems to be a problem of permissions on the /run/user/1000 directory?

[Britgirl]

We would need to see the complete server-side logs so we can check to see why you are encountering this issue. 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.

Steps to reproduce and some additional details about your set-up (OS and version, for example) would also be useful.

[Britgirl]

Hi, are you able to send us the complete 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!

[Britgirl]

Sounds like a video driver issue, something in the update you said you just did. Can you try disabling hardware decoding in NoMachine on the client side (the machine you are connecting from)?

First exit the Player on the machine you are connecting from by right clicking on the !M icon in the sytem tray and clicking Exit Player.

Edit %USERPROFILE%\.nx\config\player.cfg and set:

<option key=”Enable hardware accelerated decoding” value=”false” />

Then create a new session and check if you still have the same issue.

If you do, set the same key to:

<option key=”Enable hardware accelerated decoding” value=”disabled” />

and create a new session. The first setting disables the use of HW decoding but the codec library is still loaded, while the second settings disables completely the HW decoding. Let us know the results.

[Author]

Posts