Multiple monitors client side

[sierrajmk]

In regards to https://www.nomachine.com/FR12K02799, is this implemented only in the enterprise paid products?  I wanted to try this in my setup and do not see any options beside what was formerly available to stretch across my client displays.  I am connecting to a virtual desktop (Fedora 32 – Gnome) on my headless server from a Windows NoMachine Enterprise Client with 2 monitors.  Both sides are at version 7.0.209 and am running the free product.

[Tor]

Hi. Enter Display menu to enable “Resize remote display” option, in order to tell the remote desktop to change its size when the client window changes, then enable “Fullscreen on all monitors”.
We’ve also extended the description of the Feature Request to make these steps more clear.

[sierrajmk]

Thank you for the response.  I still see the same behavior when trying these 2 options you mentioned, that the Gnome desktop treats the 2 monitors as one giant monitor and the maximize button maximizes across both screens.  I updated to use Fedora 33 Gnome on the server side, with both the server and the Windows Enterprise Client at 7.0.211.  It is not a physical desktop that I am connecting to, but a virtual one that is created when I first log in from the client machine.  Was this feature implemented in the free for personal use version of the product?

[sierrajmk]

Bumping this thread.  The server side is still only seeing one monitor and when I hit “Fullscreen on all monitors” it just stretches the display across both instead of treating it as 2 monitors.  Please see previous posts in this thread for my setup, as I am connecting to a virtual desktop on a headless machine.

[Tor]

Hi. Can you please send for debugging client side logs (%USERPROFILE%\.nx) and the output of the command xrandr -q executed in a session, after trying to enable the multiple monitors fullscreen? Mail everything to forum[at]nomachine[dot]com. Thanks.

[sierrajmk]

Sent as requested.

[Carin]

The logs were received but the Feature Request in question (and what you are trying to achieve) is implemented for Terminal Server Products and only works when creating a virtual desktop. These virtual screens, matching client-side screen, could not be implemented on a physical desktop.

[Author]

Posts