Forum Replies Created
-
AuthorPosts
-
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 #9215
BritgirlKeymasterThanks 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.
BritgirlKeymasterDid 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).
BritgirlKeymasterWe will be sending you an email soon with further instructions.
BritgirlKeymasterIn the meantime we have also notified Oracle. It appears to be something that may well need to be fixed on their side. Of course, if there is a fix that we can implement, we will post any info here.
BritgirlKeymasterWhat Linux distribution and version are you using on the PC at work (the server)? Client OS which initiates the connection ? – useful to know for replication during investigation.
BritgirlKeymasterSimilarly to what was suggested above you could try updating the driver.
-
AuthorPosts
