Forum Replies Created
-
Posts
-
Closing the window of the player has the same function as the ‘Disconnect’ button in the menu.
Regarding latency, bandwidth and other benchmarks, it can depend on a combination of factors such as what you want to use the connection for, if it’s on a VPN or not, etc so please consult the following:
Guidelines for sizing a NoMachine infrastructure and benchmark tests for v. 6
https://www.nomachine.com/AR02P00966For making your own tests, see “Reading NoMachine statistics”
https://www.nomachine.com/AR02N00875Maybe nxnode is not added to Accessibility or Screen recording? Did you check that? Some tips are here: https://www.nomachine.com/AR11Q01061
If not, it could be this problem:
‘No available sessions’ is issued when connecting to the Mac login screen
https://www.nomachine.com/TR02R09535Is this a recent install? If so, did you reboot after installing?
What happens if you click ‘Start the server’? Does it start and then stop?
What do logs show? Similar topics are:
https://forums.nomachine.com/topic/server-doesnt-start-on-windows-10
https://forums.nomachine.com/topic/windows-10-failed-to-start-nxserver-processSo your solution is to adopt Graywolf’s suggestion in 1c 🙂
the software could have detected that no monitor at all was configured in my setup and react in some way
It’s a bit difficult to predict that it won’t work even if there is no monitor detected (the combination of GPU model, the software driver, the OS etc). The answer is to force the set-up to use our virtual display even when it might not be necessary, that’s not what all users want.
We haven’t been able to reproduce the problem unfortunately (although we are still trying). We are currently making some changes to initialization of desktop duplication which we use for capturing screen, and we think this will help your case when these get released, most likely in version 7 onwards.
NoMachine doesn’t show the session at native resolution, but Retina will be fully supported soon, please see the Feature Request here: https://www.nomachine.com/FR02M02864
Mantoshelis, you may have read my follow up in the topic that Kroy linked in his reply. As mentioned there, we are investigating a number of issues with Arch-based distros (currently unsupported by the way) to see if they can be fixed in a relatively straightforward way. For now, users can adopt the workaround suggested. Thanks for your patience.
We would need you to enable debug in the logs in order to understand why NoMachine is not recognizing the disconnects correctly. Please follow the instructions here, https://www.nomachine.com/DT11R00182, on the computer you are connecting to and when you’ve replicated the behaviour, extract the logs and submit them again. Thank you.
Whilst our developers investigate the potential fix, you could consider reverting back to the previous update if possible (1909 or earlier).
We are aware of this issue and a Trouble Report has already been opened. Please follow this link https://www.nomachine.com/TR10R09864 and then use the ‘notify me’ box next to the TR to sign up for notification of the fix when it is released.
A link to the download was sent.
A package with the patch is available for those who encounter the problem described in this topic.
You can compare the free version and its enterprise-oriented sister product here: https://www.nomachine.com/remote-access-for-everyone. You should be looking to install Enterprise Desktop on the computers you want to access if you or your client are using the software in a commercial environment. Contact Sales for more info about this and the differences between the two products for your specific needs.
Disabling the screenshot feature is possible by preventing access to the “Connection information” dialog. Take a look at the ClientMenuConfiguration key in the server.cfg and remove “connection”.
Regarding your comments about our online knowledge base, we are already working on improving this by removing/moving documentation which can now be considered irrelevant (such as articles etc about our legacy products 3.5 and version 4). In an ideal world there wouldn’t be any need for support 🙂 but that proves to be a an impossible feat even for providers of operating systems, let alone for the ISV’s that make the programmes to run on them. All the more reason to make sure help resources are easy to find. In any case, we appreciate the feedback you’ve provided because it gives us some extremely useful insight into what users of our software are experiencing, so thank you!
Look out for version 7, coming soon, which will provide a streamlined UI, making navigation of the player and server components as well as connection creation/configuration much simpler.