Forum Replies Created
-
Posts
-
Restart isn’t necessary 😉 Sorry if that wasn’t specified, but glad to hear the issue is now fixed.
Our internal tests show there a number of issues with using NoMachine on XP, and we are currently investigating how and if it’s possible to fix them. As soon as we have some news we’ll post it here.
Thanks for reporting. We’ve opened a TR here: https://www.nomachine.com/TR07N07047
Use the ‘notify me’ check box to know when a fix has been released.
This isn’t possible at the moment and would require some design changes. A custom implementation might be feasible here. You should contact the sales team (see Contact Us in footer and select Sales Enquiries) and provide more details about your requirements.
We don’t have a configurator tool during installation. When you install NoMachine the default settings are applied which should satisfy the majority of set-ups security and functionality-wise 🙂
Are you configuring multiple NoMachine clients and are looking for a quicker way to configure them all? If so, then propagating the cfg file to all clients could be a solution. The simplest way to do that is to configure the NoMachine host via the GUI (the PC you want to access), then copy the server.cfg and node.cfg to all the other hosts (the other machines you want to access). On Windows these files are in C:\Program Files
(x86)\NoMachine\etc. The guide here shows you what you need to enable/disable via the GUI https://www.nomachine.com/DT11M00107.I am not sure what else you want to configure a priori because others might be related to the player side i.e the connecting client. If you list them, we can provide further guidance.
Ideally we would need logs from the affected remote desktop session from the upgraded installation (if that’s possible)? Instructions on how to enable debug are here: https://www.nomachine.com/DT07M00098. We can also prepare a debug package for you to install if you are willing to help us investigate, we’ve tried to reproduce on a replica of your set up, but to no avail.
Also, does disconnecting and reconnecting help or does the session still stay unresponsive to clicks?
The TR associated with this forum post was closed in the software release 5.1.40. Everyone, please update. https://www.nomachine.com/TR06N06907
Please send us the logs from ProgramData/NoMachine/var/log directory with increased debug level. Details on how to increase the level of debug are here:Â https://www.nomachine.com/DT07M00098#3
Send to forum[at]nomachine[dot]com
If there is a bug on Fedora 24 when using the free version, it will also be in the Enterprise Server installed on Fed 24. The only difference between those two products is that the latter lets you run virtual Linux desktops. The free product lets you connect to the physical display.
Please submit the logs that you failed to attach, that way we can check. (preferably both client and server sides). Thanks!
Provided you have installed one of the products with the virtual Linux desktop functionality (e.g Workstation), follow the steps here: https://www.nomachine.com/creating-new-virtual-desktop-sessions
Please send the logs direct to forum[at]nomachine[dot]com. They may have been too big to be attached here.
We received the Player side logs. We will need to check the server side logs (the whole /usr/NX/var/log directory is better). Please see the instructions here on how to enable and extract them, https://www.nomachine.com/DT07M00098.
Then send them on to us as you did before. Thanks!
There is a Trouble Report open for this issue: https://www.nomachine.com/TR12L04740
Please use the ‘notify me’ option to receive an email from us when a fix has been released.
Please refer to https://www.nomachine.com/DT07M00090 section 7.2 Managing sessions.