Forum Replies Created
-
Posts
-
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.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
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.cfgthen you should execute:
chmod 644 /etc/NX/server/localhost/node.cfgThis last operation will require admin privileges,
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.
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.
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 ?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.
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 --restartHi, just so that we have a clear picture of your set-up. Can you tell us the NoMachine product that you have on the Red Hat server?
Hi, can you tell us what operating system you are connecting from and connecting to? Are you running the latest NoMachine 8.6 on both sides?
Have you seen the article in our knowledge base that explains how to set up port-forwarding? (section 3. Troubleshooting for most common cases requiring manual configuration of the router)
https://kb.nomachine.com/AR04S01122
It could be that you have a double NAT and in that case port forwarding must be configured manually on both routers (your home router and your work’s computer)
Ilgaz, did you mean to write for this topic, or the other topic here:
https://forum.nomachine.com/topic/no-hardware-decode-on-kubuntu-22-04-gtx-1060-6gb/page/2 ?Please see my response from June 27th in this thread (#post-44716).
This is not a NoMachine issue. However, a workaround is to disable hardware decoding in the player. This is done in the following way:
– close all nxplayer processes
– open the $HOME/.nx/config/player.cfg file
– find the “Enable hardware accelerated decoding” key and change it to look like this:
<option key=”Enable hardware accelerated decoding” value=”disabled” />