Forum Replies Created
-
Posts
-
Did you reboot the Windows machine after installing NoMachine? Have you tried uninstalling, reinstalling and rebooting?
Failing that, you should submit the logs of the affected Windows server machine to forum[at]nomachine[dot]com. For instructions, see here: https://www.nomachine.com/AR10K00697.
You have mentioned that the server is virtual; what hypervisor is it?
Can you confirm that you have 6.9.2 on both the client and the server side? Is the Raspberry on the server side, client side or both? What characters are showing up instead?
You don’t have to enable this option for nx user. User nx is created without password but this command from a terminal:
sudo dscl . -create /Users/nx AuthenticationAuthority ";SecureToken;"will add this user to filevault and avoid problems with the passwords.@Icebird, can you submit a separate topic with details of the error you are getting, a screenshot would be useful. Thanks!
Hi Mick, see here:
Reserved names for NoMachine programs
https://www.nomachine.com/AR01N00871Does this answer your question?
If you have a subscription, maybe you should contact our support team or sales team which can advise you on what your options are for your specific scenario.
Hi, at the moment it’s not possible, but there is a Feature Request that will most likely satisfy your requirement once it has been implemented.
Monitoring and administering the federated servers from the Cloud Server
https://www.nomachine.com/FR10Q03883Hi, this is still under development. Please sign up to receive notification of when it has been implemented (‘notify me’).
You can share a link with us to a file-sharing service – send the link to us privately via forum[at]nomachine[com] and we’ll download it.
Or are you actually still using that version (custom 6.8.1) we sent you? It is that package which contains the fix, and at the time, when you tried it, you said it was much better.
I updated the closed topic because I wrote the patch had been released, when in fact it hasn’t. Sorry if that was misleading.
The package link is still available if want to go back to using that version.
The TR has just been updated. Apologies for the confusion.
I confirm that screen blanking doesn’t work when remoting in to a Win 10 (update 1909) with two or more monitors.
Enterprise Desktop simply shows you the physical display of the remote system, so you’ll need to set up the remote system to have two monitors. To do that, you could try following the suggestion here: https://unix.stackexchange.com/questions/378373/add-virtual-output-to-xorg and see if that helps.
If you were using Workstation (from the Terminal Server family which supports multiple virtual Linux desktops), with the implementation of this Feature Request, https://www.nomachine.com/FR10N03220, you will be able to treat those multiple monitors on the server side as separate windows on the client side. This feature is in its final stages at the moment and will be released in a future update.