Forum Replies Created
-
AuthorPosts
-
BritgirlKeymaster
Hi, NoMachine runs on El Capitan. There is a known issue which you can check out here:
https://www.nomachine.com/TR10M06094
Can you send us those attachments to forum[at]nomachine[dot]com, so we can confirm if it’s the same?
BritgirlKeymasterWhat you need is the Workstation for Linux, if what you want is a virtual desktop on Linux. Take a look at the following:
What is the difference between physical desktop and virtual desktop?
https://www.nomachine.com/AR10K00700Differences between NoMachine for Linux and NoMachine Workstation for Linux
https://www.nomachine.com/AR10K00702BritgirlKeymasterThat 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.
December 11, 2015 at 09:28 in reply to: Cloud Server v5 – embedding NoMachine, customer branding #9316BritgirlKeymasterIn 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.
December 4, 2015 at 10:49 in reply to: Black screen while attempting to connect to Gnome Ubuntu 15.10 #9263BritgirlKeymasterYes, the latest version contains the fix. Everyone please update your software.
BritgirlKeymasterThe fix for that is actually planned for the next release, so currently going through QA.
BritgirlKeymasterThere 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
December 1, 2015 at 12:29 in reply to: Upgrade failure 5.0.43 to .47, Linux Workstation license #9215BritgirlKeymasterThanks for letting us know.
BritgirlKeymasterPlease update your software. The Trouble Report was fixed in 5.0.53.
BritgirlKeymasterThe fix for this TR was released in version 5.0.43. Please update if you haven’t already done so.
BritgirlKeymasterCan you send us the logs? Please check this document for instructions.
https://www.nomachine.com/DT07M00098Send them to forum[at]nomachine[dot]com.
BritgirlKeymasterThe 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.
BritgirlKeymasterThanks 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? 🙂
BritgirlKeymaster@imans, see the thread above. If possible, send us the additional information that Tor has already requested. Thanks!
BritgirlKeymasterIt 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.
-
AuthorPosts