Britgirl

[Britgirl]

A portable package is planned and work was already started. We had other priorities in the meantime though and work was temporarily suspended.

[Britgirl]

We are not aware of a similar problem.
So that we can attempt to reproduce, please tell us:

1) macOS version on affected machine
2) NoMachine version on affected machine

[Britgirl]

You can try to see if that helps.

[Britgirl]

It looks similar to this problem:

Xorg crashes after certain events sequence
https://www.nomachine.com/TR07U10939

Please check if setting the following key in node.cfg helps:

DisplayServerExtraOptions "-eventdelay 0"

 

[Britgirl]

Can you attach the screenshot which didn’t attach? Don’t paste, but use the attachment tool “Upload attachments”.

Also, tell us:

– did you update from an earlier NoMachine version?And what version are you using now?

– specify the OS client side and also server side.

In NoMachine version 8, UPnP/NAT-PMP is disabled by default in the Free Edition. To get access to your computer over the internet, NoMachine’s UPnP/NAT-PMP port mapping must be enabled by hand (‘Server settings -> Ports’ -> Select the service and click on Configure); or alternatively, your router can be configured with the appropriate port-forwarding rule.

[Britgirl]

Hi, we aren’t able to reproduce the issue – we checked with all the latest Win 11 updates as well.

We will need logs with debug enabled from the Windows you are connecting to (the one which keeps turning “desktop shared” on and off).

Please follow the instructions here for Windows:

First Step: Enable Debug Level on the Problematic Server/Node Host
https://kb.nomachine.com/DT07S00243

Once you’ve enabled debug, go to your other Windows machine and start a connection. Reproduce the problem. Gather the logs.

You can send your attachment to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.

[Britgirl]

Custom scripts are available in all NoMachine server products, but there is not one suitable for what you’d like to achieve at the moment. We are evaluating the possibility of adding it. Check out the guide here for a full list (11.3. Server Automation Interface: Custom Scripts executed on Server/Node Events) of what is available: https://kb.nomachine.com/DT07S00246
You can achieve the same also in the free version if you are using that on the server.

However, you could probably achieve a DHCP hook using your own system’s scripts to find and set the new IP as NXdListenAddress key in server configuration file, and then run /etc/NX/nxserver --configupdate.

[Britgirl]

When a NoMachine server runs on a machine, it makes a list of network interfaces, and it collects all the information (hostname, list of IPs, ports on which it is listening) and sends it on the LAN to the NoMachine clients (on the same LAN). This info is used to create an mDNS item in the list of IPs and they are transmitted to the Player. As you correctly wrote, these machines are “autodiscovered”. How does the Player know that you want to use 192.xx or whatever rather than another?

What you can do is go in to the Player’s Configuration panel of the connection and manually choose the correct IP address from the list, by editing the mDNS machine before connecting. See https://forum.nomachine.com/topic/how-to-make-nomachine-update-target-computer-ips#post-40814

 

[Britgirl]

The logs show: “cannot open file `/etc/NX/server/localhost/node.cfg’ for reading (Permission denied)”

This is what you should change to make it accessible to “read” for all users

Execute:

ls -l /etc/NX/server/localhost/node.cfg
-rw-r--r-- 1 root root 605 cze 30 15:03 /etc/NX/server/localhost/node.cfg

then you should execute:

chmod 644 /etc/NX/server/localhost/node.cfg

This last operation will require admin privileges,

[Britgirl]

Hi Piter, we are going to send a debug library, please check your inbox. If you have any questions about the library, simple hit reply to our email.

[Britgirl]

Well, Wayland is still very much in development, especially for KDE, and practically every release of every distribution changes things and NoMachine then has to adapt. So it’s not that there is no lack of support in NoMachine 😉

As for this specific issue, the fix will be in the next available maintenance. It did not make the 8.6 release last week.

[Britgirl]

We have not been able to reproduce this problem when connecting from either client v7 nor 8.6.
Please confirm the nginx version and which specific macOS ?

[Britgirl]

Do you get the same problem if you connect from an Enterprise Client version 8.6?

[Britgirl]

Hi, the server settings path cannot be changed. It’s a global setting, one place for whole server host. The Player settings are per user, and that’s why you can change the path. What you can do is install the NoMachine server software to a different location.

[Britgirl]

Everybody, there is a workaround, and it’s the same as the one we reported for the topic here: https://forum.nomachine.com/topic/session-terminated-unexpectedly#post-41758

Quoting what I wrote there: We recently discovered a similar issue but only when using Linux Mint in a VM. Please edit /usr/NX/etc/node.cfg and set following key:

DisplayServerExtraOptions "-eventdelay 0"

and restart nxserver:

sudo /etc/NX/nxserver --restart

[Author]

Posts