Britgirl

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

[Britgirl]

Hi, can you confirm that the check box “Start the server at system startup” is showing as enabled? Go to ‘Server setting’ on the affected computer, open NoMachine and proceed to Server settings -> Status -> just below “Restart the server” there is the checkbox.

[Britgirl]

Logs show multiple lines like:

mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(13): Permission denied
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
(pam_mount.c:522): mount of Programme failed
(mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(13): Permission denied
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
(pam_mount.c:522): mount of iso-images failed

Why this is happening, we can’t say. It indicates problems with your system, and not NoMachine, given that on your other server, everything is working without any issues.

[Britgirl]

Hi,

Enterprise Desktop (on all supported platforms) is for accessing the physical display of the computer you want to access. On Mac and Windows it cannot create virtual displays. The exception is on Linux.

In the case of Linux, when connecting to the physical desktop which doesn’t have an X server running (e.g. it’s a headless machine), NoMachine is able to use its own display service (which is an embedded X server) to let users connect seamlessly to a physical desktop running in the background on the remote machine, what we call a “virtual display” or “virtual desktop”.

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 “nomachine virtual desktops” on the same host.

Further references:
https://www.nomachine.com/terminal-server-family
https://www.nomachine.com/product&p=NoMachine%20Workstation

[Britgirl]

A more elegant solution is using DDNS. Then you could use a domain such as mynomachine.ddns.net, but for that you need to configure a DDNS service on the server side.

I don’t see a solution other than changing the entry in the connection configuration file on client side.

[Britgirl]

To know where a user is connecting from, you can look in the nxd log which shows for example “Info: Connection from 192.168.68.192 port 46684 process 22708 started on Fri Nov 18 05:50:37 2022.”.

 

/usr/NX/var/log/ on Linux
%PROGRAMDATA%\NoMachine\var\log\ on Windows
/Library/Application Support/NoMachine/var/log/ on macOS.

[Britgirl]

The logs don’t indicate any issue with NoMachine software. Rather there are multiple reconnects which would indicate problems with your network. Statistics show high latency which also indicates network issues. We can see “268 ms latency 5s, 221 ms latency 30s”.

For 5 seconds there was an average of 268 ms latency and for 30 seconds there was an average of 221 ms latency, so you should looking in to your network conditions. It might not even neccessarily be a bandwidth problem, but maybe some other bottlenecks like router, switch, or network card even. Maybe you could do a ping and traceroute and monitor them when you’re reproducing the problem.

[Britgirl]

You need to forward port 4000 to the local IP of the first Mac and 4001 to the second Mac’s local IP 🙂

[Britgirl]

This is not currently possible, but is planned for a future release.

In the current version, when the user has multiple monitors on the client, it is possible to choose if the NoMachine virtual Linux desktop session has to be spanned on all monitors so that the virtual desktop sees this as one giant monitor, or if each monitor can be treated as an individual monitor. The difference is in the first case when you for example maximize a window, it spans on all monitors. In the second case separate monitors let you drag windows between monitors. Maximized applications only span one monitor.

[Britgirl]

We haven’t been able to reproduce this behaviour, so we ask users who were encountering this issue to update to the latest 8 and open a new topic if the problem is still there, so that we can start a new investigation. This topic is going to be closed.

[Author]

Posts