Britgirl

[Britgirl]

Hi,

NoMachine server, and its corresponding license, is installed once on the machine which is running the desktop you want to access. In your case, a subscription license for Enterprise Desktop gives you access to the physical display on that host. If there are multi-monitors attached to that remote desktop (server-side), NoMachine will detect this in your remote desktop session and let you switch between the monitors. See here for more information:

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

If you prefer to start separate connections (so 3 in your example) to that desktop, they will all be connected to the same physical desktop, but as separate sessions each one will be able to view a different monitor.

I already tried ConnectPolicy autocreate=1,autoconnect=1,automigrate=0,desktop=0,dialog=0 on a Windows system, but still when I remote in, it disconnects the first connected session.

 

This key is for NoMachine virtual desktop sessions when connecting to NoMachine Terminal Server Products, so you should ignore this key. Have you already tried the evaluation ED or have you installed the free edition? Installing the Free Edition on the remote computer you want to access allows one connection.  And so if you try to connect a second session, the first one will close.

[Britgirl]

Thanks for the update.

[Britgirl]

If we create a virtual desktop such as with the workstation for Linux, can we define multiple virtual screens/monitors and display them through NX.

Yes. Workstation, like all of the products from the Terminal Server family, lets you run multiple instances of a Linux desktop on the same server. NoMachine terminal server products for Linux will also treat multi-monitors on the client as separate monitors in virtual desktop sessions. This means that when the user chooses to span the NoMachine player window across all client-side monitors, remote applications will see the same layout of monitors and can be maximized to a single monitor. See more about this here:

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

If you have multi-monitors on the server-side and connect with NoMachine to the physical desktop (whether it’s a VM or physical hardware), it’s not currently possible to have each of those monitors display to an individual screen on the client side. It’s planned, but we can’t give you a specific version of when this will be available.

[Britgirl]

Maybe the low resolution the headless physical display had was the cause of the KDE problems. Glad to know you’ve solved your issues anyway. Although I’m not quite sure if you’ve resolved the “black screen” or “missing kde taskbar” 🙂

[Britgirl]

Currently the client follows the selected DPI when painting on screen. In the future we are consider implementing an option to ignore the DPI. But this is still being evaluated.

[Britgirl]

Hi, this is related to the GPU’s capabilities.

Please consult this article from our online knowledge base:

How to solve ‘stuck resolution’ problems on headless machines
https://kb.nomachine.com/AR05S01127

“In some cases users can get only a small screen resolution without the possibility to change it (‘stuck resolution’).  This depends on the GPU which makes available only one resolution when the monitor is not present.

A common solution is to adopt a fake display dongle (also called ‘dummy dongle’) inserted in the video card port to simulate the presence of a screen and force the system to take full advantage of the GPU as if a real monitor is connected.”

I’m not sure what you mean by “Opening the settings on the headless windows machine also doesn’t really work because when I scroll to the desired setting only the scrollbar moves and everything else stays still.” A recording of the NoMachine session would be useful to illustrate the problem perhaps.

[Britgirl]

Hi,

we’ve just updated an article that will help with configuring your Fedora NoMachine server in an AD domain using the NX protocol.

Connecting with NX protocol to a NoMachine server on Linux in an Active Directory domain
https://kb.nomachine.com/AR12P01007

[Britgirl]

mcjev, thanks for letting us know.

If you happen to switch back to Wayland and only if you want to, enable the logs on the server side and send them to us so we can check. This would help us understand what’s going on.

See this article for instructions: https://www.nomachine.com/DT11R00182

[Britgirl]

Thanks for letting us know. We’re checking and will update the topic soon.

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

[Author]

Posts