Forum Replies Created
unfortunately there is no other way.
It’s a client side setting, the only option is to change the CFG of all clients, wherever they are.
Maybe the best thing for you could be distributing a CFG for all users, so they could copy it in $HOME/.nx/config
on their side.
Please also remember to change that setting on server side for each and every user in their “$HOME/.nx/config” directory.
I’ve logged into all five of our servers running NoMachine and confirmed that the “Don’t show other computers on the network” player preferences setting was already unchecked. Also verified all servers had the “Advertise this compute on the local network” setting unchecked.
It’s correct that the key “Advertise this compute on the local network” is unchecked.
However, another key “Don’t show other computers on the network” should be checked.
So please change that to be checked (like in the screenshot 2).
To stop all MDNS traffic, you should have on player’s services panel on each host like screenshot 1,
and on the Player preferences like screenshot 2.
Are all your players and servers set to this?
The important thing is that you apply them an all machines of your network on which you don’t want to have mDNS.
We could not reproduce this issue in your evironment.
Please gather logs and send them to us. Please follow the article on how to enable debug:
https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)
Then please do:
sudo /etc/NX/nxserver --restart
and reproduce the problem. Then please gather the logs either manually or by executing:
sudo /etc/NX/nxserver --debug --collect
Please send the logs to forum[at]nomachine[dot]com using the title of this forum’s thread as the mail’s subject.
I assume ‘10.156.1.13’ is the server host where you had disabled mDNS broadcasting. Those logs, suggest it is mDNS discovery.
To disable discovery on clients, select Player preferences -> Privacy -> Don’t show other computers on the network.
The important thing is that you apply them an all machines of your network on which you dont want to have mDNS.
Please make sure that you have restarted nxserver after disabling broadcasting by setting configuration key in server.cfg:
Restarting nxserver after such change is required.
Please do the following steps on all hosts where you want to disable broadcast feature.
In case restarting nxserver didnt help, please refer to an article on how to enable debug:
1 .Enable debug on the server machine and then do:
sudo /etc/NX/nxserver --restart
Then please check if you reproduced issue. Then please gather logs either manually or by executing:
sudo /etc/NX/nxserver --debug --collect
2. Please send to us server.cfg file.
3. Can you please tell us how do exactly you check that
Please send the logs and server.cfg file to forum[at]nomachine[dot]com using the title of this forum’s thread as the mail’s subject.
About second suggestion to disable broadcasting from GUI by uncheck the box “Advertize this computer…” in the player’s services,
looks like you have set key ‘EnableServerPreferences’ to 0 in
Please make sure that this key is set to ‘1’ and restart nxserver to be able to see “Server Preferences”
# grep EnableServerPreferences /usr/NX/etc/node.cfg EnableServerPreferences 1June 3, 2020 at 10:38 in reply to: Nxhtd webserver did not start anymore after changing the ports #27944
This is a known issue. Please consult the Trouble Report, there is also a workaround available.
“The NoMachine web server doesn’t start on Ubuntu 20.04 after changing the ports”
Additionally there is an Article which may be helpful:
“How to change default ports for nxhtd”
If the NoMachine network daemon (nxd) is configured on the server to listen on a different port,
it’s also necessary to update the client.crt file, on Linux /var/NX/nxhtd/.nx/config/client.crt, to have:
Host:localhost 5001 -----BEGIN CERTIFICATE----- (...) -----END CERTIFICATE----- Host:127.0.0.1 5001 -----BEGIN CERTIFICATE----- (...) -----END CERTIFICATE-----
You can find whole instruction in here:
https://www.nomachine.com/AR06N00888May 21, 2019 at 09:35 in reply to: No external IP address on Fedora 29; present on Win10 #22397
Hello (pasting some info from your email reply)
1 “both the machines are connected to different routers, now also on the Linux end there is a new router.”
– did you checked that on both UPnP is enabled?
– what is the new router name/model?
2 “However, one’s a laptop, so I can move it to the other location —
when I have them both on the same home network, the
connection works fine.”
And what about UPnP on that laptop in the new location?
As I understood Windows is installed on this Laptop, and in its base location
UPnP is working.
When you move this laptop to the place where PC with Linux is located
does UPnP works or now it doesnt?
3 Just for a test, could you disable/turn off all other network interfaces on the Linux machine
and leave only WiFi or cable connection alive to this router. And then please call as administrator in terminal
/etc/NX/nxserver --restart /etc/NX/nxserver --upnpstatus
if still doesnt show, wait a while and run:
Please send all the output to forum[at]nomachine[dot]com making sure to reference the topic.May 9, 2019 at 14:12 in reply to: Error "Failed to authorize the server certificate" with NX version 6.6.8 webplayer #22262
we would need some more information
1 Could you please send to use all configuration files *.cfg from :
If you don’t show us the htd.cfg, it’s hard for us to advise appropriately.
2 Please execute this command in terminal:
# /etc/NX/nxserver --version
3 From server.cfg I can tell 2 things
3.1 HTTP is disabled
# # Specify how clients will have to contact the node, by default by # the NX service. To allow for multiple methods, specify them in a # comma-separated list. Supported methods are: NX, SSH and HTTP. # ClientConnectionMethods NX,SSH
to enable you have to add HTTP:
Restart of nxserver is required.
3.2 it looks like this is old version maybe v5, if thats true is this possible to update to latest v6?
4 We would ned alos to see all logs.
Instructions about debug and collecting logs you can find there: https://www.nomachine.com/AR07K00677
Please send them to forum[at]nomachine[dot]com making sure to reference the topic.May 6, 2019 at 09:04 in reply to: Error "Failed to authorize the server certificate" with NX version 6.6.8 webplayer #22220
can you please describe what are you trying to do by removing ssl certificates,
is it because you want to have only HTTP or both HTTP and HTTPs instead of only having HTTPs?
Can you also send to us htd.cfg and server.cfg configuration files.
Please send all the info to forum[at]nomachine[dot]com making sure to reference the topic.April 9, 2019 at 16:30 in reply to: No external IP address on Fedora 29; present on Win10 #21989
we would need some more information:
1 When did you notice that UPnP stopped working ? Maybe after a software / OS update?
2 Can you describe the network infrastructure
– router model / version
– is there more than one router / network interfaces on which Linux machine is connected?
– is the computer directly connected to router or is there a cascade or repeater between them?
– are both machines [ physical machines or virtual [vbox/vmware] ? ] connected to the same router, both over wifi/lan or mixed?
3 Can you please execute those commands:
– on Linux machine in terminal:
nmcli device status route -n ifconfig -a
– on Windows in cmd:
Please send all the output to forum[at]nomachine[dot]com making sure to reference the topic.
not sure if you’re referring to the certificate for the web server. If so, edit the nxhtd configuration file to point to the new certificate.
If, on the other hand, you’re referring to the certificate for NX authentication, it still has to be implemented
currently for a Web session you can use self-signed certificates, as explained in:
CA certificates are effectively not supported yet.
NoMachine retrieves the public IP and maps the port automatically when the router supports UPnP or NAT-PMP port mapping.
Information how to enable UPnP port mapping on nxserver is available here: https://www.nomachine.com/AR11L00827. Just set
When IP will change you will probably not be able to connect to the server. It’s now been queued up for fixing and you can see it here: https://www.nomachine.com/TR01P08354. You can use the ‘notify me’ tool to find out when a fix has been released.
However there is a way to handle this, and make it works:
when IP will change you can use script or by hand call those 2 commands as administrator / root user:
# /etc/NX/nxserver –upnpunmap
# /etc/NX/nxserver –upnpmap
If UPnP is enabled and works on router that server machine is connected you will see as the ouput of second command external IP and Port.
Port may not changed, but those to commands called exactly in that order, will allows you to connect after IP changed.
To get only information about port mapping you can call:
# /etc/NX/nxserver –upnpstatus
the ouput will be similar to:
# /etc/NX/nxserver –upnpstatus
Local IP 192.168.1.2
Gateway IP 192.168.1.1
External IP 220.127.116.11
NX port 4000 mapped to: 18.104.22.168:29382February 27, 2018 at 17:18 in reply to: Problem opening GW port in automatic at Windows boot #17700
I asked to check if UPnP is enabled just to be sure, as you want to use UPnP feature it should be enabled all the time.
1. Enable the logs by following the instructions on the server side using the article https://www.nomachine.com/DT10O00163#1 (alternatively there is https://www.nomachine.com/DT10O00162 which is a less technical version).
2. As you can see here: https://www.nomachine.com/DT10O00163#1.4.
you will find the logs on Windows in
%PROGRAMDATA%/NoMachine/var/log on Windows Vista, 7, 8, 8.1 and 10. Documents and Settings/All Users/NoMachine/var/log on Windows XP.
3. Reproduce the problem and show us the result of the following commands::
On Windows: start cmd.exe as root (Administrator) and
C:\Program Files (x86)\NoMachine\bin\nxserver.exe –upnpmap C:\Program Files (x86)\NoMachine\bin\nxserver.exe –upnpstatus
sudo /etc/NX/nxserver --upnpmap sudo /etc/NX/nxserver --upnpstatus
4. Zip them up and send them to forum[at]nomachine[dot]com. Use the ‘@’ and ‘.’ in place of the brackets.
It’s important to reproduce the problem once you’ve enabled everything and then zip the logs.