Forum Replies Created
-
Posts
-
That happens because NoMachine should be installed after installing Gnome (or any other desktop). NoMachine, at installation time, tries to detect what your DE is and set up the system to start it, without any need for the system administrator to intervene in the basic setup. This can only work if the DE is already installed and configured as the default at installation time. You can change the DE that is started by default at any time, and obviously add a new DE that is installed later.
So if you installed GNOME when NoMachine had already been installed, you need to set some keys in /usr/NX/etc/node.cfg.
To run a custom session: please modify 2 keys, DefaultXSession and CommandStartGnome into:
DefaultXSession “/etc/gdm/Xsession gnome-session”
and
CommandStartGnome “/etc/gdm/Xsession gnome-session”
Please remember to remove “#” at the beginning of the line.
If you also wish to have access to a full virtual desktop via “Create a new virtual desktop” please also change the key DefaultDesktopCommand in the abovementioned file into:
DefaultDesktopCommand “/etc/gdm/Xsession gnome-session”.
You can also uninstall NoMachine and install it again, then all those keys will be set automatically.
In its current version, customizations without the permission from NoMachine are not possible. This is something that the sales team can you help you with. I suggest you contact them using the Contact Us link in the footer of the website.
There is nothing to configure. One of NoMachine’s first priorities to work out-of-the-box is security as you can read in our online documentation:
https://www.nomachine.com/AR10K00705
https://www.nomachine.com/AR11K00739If you prefer, you can set up key-based authentication with the NX protocol as described here:
https://www.nomachine.com/AR02L00785
Alternatively, you can use SSH. This is a feature available in the Enterprise range as mentioned in article AR11K00739 above.
If you really want to go into detail about the different types of authentication that we support, check out the document about Authentication
https://www.nomachine.com/DT07M00088For your question about the broadcast feature on LAN, you can disable it. See the tutorial here: https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network
Can you send us the logs? Please check this document for instructions.
https://www.nomachine.com/DT07M00098Send them to forum[at]nomachine[dot]com.
The free NoMachine product doesn’t support SSH based connections methods.
Check that you are using the latest version with default NX protocol. This will connect on port 4000. To check that you are using the NX protocol, open the GUI, right click on the connection, and then ‘Edit’.
The output of status you pasted is correct:
[…]
NX> 162 Disabled service: nxnode.
[…]
which means that the nxserver was not able to find local X server, which is correct in case of headless hosts.
Thanks for the additional information that you submitted with the logs. We have found out what the problem is and one of our developers will update the topic soon. Can you update the forum post with what you wrote in your email? 🙂
@imans, see the thread above. If possible, send us the additional information that Tor has already requested. Thanks!
It seems you are using the legacy server version. Questions about version 3.5.0 (or earlier) are dealt with via the traditional support channels. If you don’t have a subscription and you are using the free NX Free Edition or an evaluation, please contact the team via the Contact Us link in the footer of the website and select General Enquiries.
Did you try what Tor suggested?
If you wish to use the same connection to do both virtual desktop and desktop sharing, then I’d suggest to not save the desktop type in the configuration (by checking the box “Save this setting in the connection file” in the type selection dialog).