Britgirl

[Britgirl]

I understand that on X.org everything works fine but with Wayland it’s laggy. Could you follow the suggestions in this article?

Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083

Look at the sections Option 1 “PipeWire desktop sharing provided by the desktop compositor” and Option 2″Use EGL capture”.

Please also check our notes for recommendations and tips:

Notes for connections to Linux physical desktops running Wayland
https://kb.nomachine.com/AR02P00969

[Britgirl]

If you have the lid closed on the laptop you should stop the graphic interface and use it as a headless machine. The remote session will then work as a virtual session (see this article for futher information: https://kb.nomachine.com/AR03P00973). Then connecting via NoMachine to a headless Linux, it will detect that no display is running and ask you if you want to create one.

If the lid is open, Xorg will work as it should and physical sessions will work correctly.

[Britgirl]

We’ve not been able to reproduce this problem, despite several attempts. Are you able to send us the logs from the server sideso we can take a look? Please follow the instructions here and send them forum[at]nomachine[dot]com making sure to use the title of your topic as the subject of your email.

How to gather debug logs for support requests
https://kb.nomachine.com/AR07K00677

[Britgirl]

We’ve not been able to reproduce this problem on our RPi and with snap, despite several attempts. It could be something to do with a specific setting or configuration in your Oracle VM, is this possible? Are you able to send us the logs from the server sideso we can take a look? Please follow the instructions here and send them forum[at]nomachine[dot]com making sure to use the title of your topic as the subject of your email.

How to gather debug logs for support requests
https://kb.nomachine.com/AR07K00677

Thanks!

[Britgirl]

You can install NoMachine on a headless Linux host and connect to its display. I imagine you already using this on your Ubuntu workstation. Some considerations to bear mind:

Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973

NoMachine is designed to work out-of-the-box on Linux headless machines provided a desktop environment is installed. NoMachine is able to detect when the X server is not running and run its own virtual display, which is an embedded X server. This ability, enabled by default in the free edition of NoMachine, can be activated also in the commercial versions (Enterprise Desktop).

If you want to run multiple virtual displays, and keep your applications running in all of them, try NoMachine Workstation from the Terminal Server for Linux suite. This will let you run up to 4 individual desktop sessions, all running behind the physical display. It’s also available as evaluation software.

Differences between NoMachine Free Edition for Linux and NoMachine Workstation for Linux
https://kb.nomachine.com/AR10K00702

[Britgirl]

Please follow the configuration tips for Arch-based installations which are from a separate topic:

https://forums.nomachine.com/topic/help-changing-resolution-on-connection#post-39768

I’ve pasted them here for your convenience

1. Create a backup of nx PAM configuration (sudo cp -a /etc/pam.d/nx /etc/pam.d/nx.original). Then change /etc/pam.d/nx in this way:

auth       include       system-login
account    include       system-login
password   include       system-login
session    include       system-login

2. Change DefaultDesktopCommand in /usr/NX/etc/node.cfg in order to have this on KDE:

DefaultDesktopCommand "/usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startplasma-x11"

3. Stop display manager:
sudo systemctl stop display-manager

4. Restart NoMachine:
sudo /etc/NX/nxserver --restart

Does the taskbar appear?

[Britgirl]

Hi,

NoMachine lets you connect to the physical display on the Windows machine i.e it displays an exact copy of the graphics card’s output. Connecting to a virtual display running on the Windows host is not possible. This is available in the NoMachine for Linux products i.e i) NoMachine Free Edition for Linux allows one connection to the physical display of the Linux machine and in the absence of a physical display, NoMachine can create a virtual one; or ii) in NoMachine Linux Terminal Server products which let multiple users connect to their own individual Linux desktop all running on the same machine.

See also this topic: https://forums.nomachine.com/topic/windows-terminal-server-replacement-options#post-13496

[Britgirl]

Hi,

if there were a seamless way to allow for both local and remote shortcuts, we would have already implemented it 😉

What you can do is to use Ctrl+Alt+M to minimize the NoMachine session window when in full-screen. Ctrl+Alt+K is also useful to toggle keyboard grabbing on and off, and Ctrl+Alt+0 to opens the NoMachine session menu instead of the page-peel.

[Britgirl]

But the video drivers for Radeon came up

Hi, do you mean that you’ve updated the drivers?

[Britgirl]

Hello, can you confirm which package you’ve installed? The tar.gz is the most appropriate for Arch Linux, and I would remove and install again just to make sure. We checked recently that NoMachine installs and works with Arch Linux, which it does.

Please do the following, where “nomachine-current-installation-file.tar.gz” is the name of the package you installed.

sudo /usr/NX/scripts/setup/nxserver --uninstall 
sudo rm -r /usr/NX/ /etc/NX
sudo tar zxf nomachine-current-installation-file.tar.gz -C /usr
sudo /usr/NX/nxserver --install redhat

Futher reference for Arch can be found here: https://kb.nomachine.com/AR03L00789

[Britgirl]

A known issue on macOS is the one described here: https://kb.nomachine.com/TR10S10377
It also affects later macOS versions and the workaround is to re-add nxnode in the list of allowed programs in System Preferences -> Screen Recording. A fix for this TR is scheduled for v8.

If the workaround described there doesn’t help, we would need logs from both sides if possible. Please check the instructions here https://kb.nomachine.com/DT11R00182, and submit the logs to forum[at]nomachine[dot]com making sure to use the title of your topic as the subject of your email. Thanks!

[Britgirl]

Hi 🙂

NoMachine doesn’t yet support Pipewire, this will be added in the next release.

As for reconfiguring audio settings without uninstalling, you can use the command:
sudo /usr/NX/scripts/setup/nxnode --audiosetup

[Britgirl]

Hi,

The problem appears to be in ESXi and how it doesn’t handle multi-monitors in remote connections, and not in NoMachine. In our tests of remote connections to virtual machines in VMware ESXi environments, the multiple monitors feature is not supported (in VMware).

https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-6-7-Multiple-Monitors-for-VMs/td-p/2748906

NoMachine connects you to the desktop environment that’s installed on the remote host. That desktop can be a physical one or it can be running in a VM, it doesn’t matter. You will connect to the physical display/monitor running there. In the case of a headless Linux, so no physical monitor attached, NoMachine is able to create a virtual display for you. NoMachine also lets you switch between those displays if it detects multiple displays or monitors available there:

https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session

If you also have multi-monitors on the client side, and you need to connect to multiple virtual displays on the server side, you could try NoMachine Workstation which provides the functionality of “NoMachine virtual desktop sessions”.  Read more about this here:

How multi-monitors on client side work when connected to a remote desktop
https://kb.nomachine.com/AR06S01131

[Britgirl]

Hi, virtual displays running Windows are not detected by NoMachine. This feature is available for the Linux operating system only.

When connecting to a Windows host/instance where you have installed NoMachine or Enterprise Desktop, you are connecting to its physical desktop, so on the client-side we only mirror the existing desktop with its physical display. If the computer you are connecting to has physical monitors attached, in that case NoMachine detects them and lets you switch between them on the connecting client side (https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session).

[Britgirl]

Hi,

thanks for taking the time to report this. The GUI preference changes don’t currently support pam_google_authenticator but we will be adding it in one of the next releases. In the meantime you can continue to edit the CFG files as you have already been doing.

[Author]

Posts