Britgirl

[Britgirl]

Hi BriBri,

you can of course request an extension with the sales team if you go to the footer of this website and click Contact us -> Sales enquiries and submit your request there.

Regarding the error that you reported, we have reproduced it and would like to send you a fixed package to test. Can I assume you are using Enterprise Desktop for Windows?

[Britgirl]

So that’s certainly good news. Thanks for providing feedback and do keep us updated if things change 🙂

[Britgirl]

We will need to see logs from the affected Windows server. First enable verbose 7 in the server settings (Settings -> Server -> Server status) on the Windows 11 machine and restart the nxserver. Reproduce the problem.

Then find the \NoMachine\var folder which on Windows is generally at this path: C:\ProgramData\NoMachine\var\

and create a zip file of it.

Then find

C:\users\USERNAME\.nx

and zip up that folder as well.

Send both to us using forum[at]nomachine[dot]com. Please use the topic’s title as the subject of your email. Thanks!

 

[Britgirl]

Everyone encountering this behaviour please update to the latest v8.2.3 and open a new topic if necessary.

[Britgirl]

This is now closed because we got no response.
Please download the latest version (both sides) and let us know if you continue to have issues.

[Britgirl]

As far as I understand, now that “NoMachine Enterprise Desktop” provides virtual desktops to also have multiple virtual monitors there.

No, Enterprise Desktop does not create multiple virtual desktops. As I wrote before, in the case of headless Linux, it can create one virtual display for you. Enterprise Desktop cannot create multiple virtual displays on Linux. To do that, you need one of the products from the NoMachine Terminal Server for Linux suite e.g Workstation. Workstation can run up to 4 individual “nomachine virtual desktops” on the same host.

That said, we have a feature planned to allow users to handle multiple monitors connected on the server as separate windows on the client side. ie. display each remote server-side monitor in a separate window.

For real physical monitors connected on the server side (which is not your case I believe), take a look at the tutorial here: 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. Our tests also reproduced this issue and it will be fixed in the next maintenance.

Trouble Report is documented here: https://kb.nomachine.com/TR09T10609

[Britgirl]

If I understand what you mean, when the user has multiple monitors on the client, it is possible to choose if the virtual desktop (with Terminal Server products) has to be spanned on all monitors, so that the virtual desktop sees this as one giant monitor, or maximized to one of the monitors.

In the first case when you for example maximize a window, it spans on all monitors. In the second case each monitor is treated individually and maximized applications only span one monitor. You can also drag files or application windows between monitors.

To enable it:
– Open the NoMachine menu panel inside the session (ctrl+alt+0 or click on the page peel in the upper right corner of the window)
– Click on ‘Display’
– Click on ‘Resize remote display’ then on ‘Fullscreen on all monitors’

To access this feature you need to have a NoMachine Terminal Server Product installed e.g NoMachine Workstation. You should first uninstall Enterprise Desktop and then proceed to install Workstation.

[Britgirl]

Same thread as: https://forums.nomachine.com/topic/no-sound-with-pipewire-and-el9

The only workaround until we add support for Pipewire in virtual display sessions is to install PulseAudio and use that.

[Britgirl]

Yes, using a combination of groups and profiles. You can block copy and paste in profiles for specific user groups.

All NoMachine Enterprise server products support groups, so you can create your group and then set a redirect based on IP address for that group.

--groupadd(there is also –-groupedit, --grouplist)
`Create a NoMachine group and then add users to the group via the
–useradd command. Use –redirect to set IP or hostname and port
for the NoMachine server where connections run by users belonging
to that group are forwarded.`

Then, using profiles, you can disable features for your newly created groups.

Profiles are available in the following products: Cloud Server and Enterprise Terminal Server. By creating rules on the Cloud Server (any of the Cloud Server range), you can propagate them to server nodes.

See here for example: 4.5. Setting Profiles for the Nodes (Rules Propagation)

https://kb.nomachine.com/DT08T00265#4.5

[Britgirl]

You could try setting this key DisableUsernameConversion 1 in the server.cfg file.

[Britgirl]

Hi, apologies for the delay in following this up. Tests here, based on logs, were not able to reproduce the issue you are encountering. What we suggest is to update to the latest version and tell us if you are still encountering the same problem. We will then start a new investigation on the latest version and we can also start a new topic.

[Britgirl]

Thanks for letting us know. We’ll consider this resolved and unrelated to NoMachine.

[Britgirl]

Unfortunately not. The only workaround until we add support for Pipewire in virtual display sessions is to install PulseAudio and use that.

[Britgirl]

Hi gbelmont22,

thanks for sharing your story with us. We feel your pain 😛

As much as we would love to be able to “create a display” on macOS, which would be what we call a “virtual display” in NoMachine jargon, it’s not because it’s a limitation of NoMachine, it’s because we can’t even if we wanted to. As you probably know already, given you’re running NoMachine on Linux, a virtual display (so, headless in your particular case) is possible with NoMachine for Linux products. When NoMachine can’t find the X server on a Linux host, NoMachine will create its own for you. This is not possible with macOS or Windows.

When you write “plugging a physical HDMI monitor into the MacBook Pro does help and the connected client starts showing content as expected but the performance is terrible”, are you referring to the NoMachine session?

What macOS version are you using, it would be useful to know.

You could try inserting the following key in the node.cfg file DisplayServerExtraOptions "-nostreamgrab" which disables the method we use to capture the screen in more recent Mac versions and enables the legacy method. We can’t guarantee that it will work, but it’s worth a try.

Let us know 🙂

[Author]

Posts