Forum Replies Created
-
Posts
-
A 30% of CPU consumption when a session is running is normal. If you have high CPU usage when you are not running sessions, please enable debug and then reproduce problem. Send the var/log directory and .nx directory located in userhome of desktop’s owner. Thanks.
Permission is not requested if the user that is connecting is the owner of the desktop session. Does this answer your question?
The log files were both damaged. Please resubmit to issues[at]nomachine.com referencing the topic.
Additionally, in your forum post, please provide more details about the version of the NoMachine products you are using (see list below). Thanks.
I use this machine to remote to other machines
If you only want to connect from this Windows machine and not also to it, it’s enough to install Enterprise Client for Windows.
This thread has two related Trouble Reports:
https://www.nomachine.com/TR04L04376
Cannot authenticate to change server settings when the username
contains a dashhttps://www.nomachine.com/TR04L04375
Cannot connect to the physical desktop on OpenSUSE 13.1 when there is
the login screenBoth have been fixed.
The team just opened a Trouble Report: https://www.nomachine.com/TR06L04456
Use the above link to track its status (it should make the next software update).
This is a duplicate of https://www.nomachine.com/forums/topic/authentication-errors-on-nomachine-server. Please refer to this post.
The client could be disabled by replacing the file ‘/usr/NX/bin/nxplayer.bin’ with a script doing only this:
#!/bin/sh
exit 255
The old file can be renamed and have permissions that don’t allow users to execute it.
This change will affect the NoMachine tray menu because
a) the menu items related to session starting will no longer work
b) the configuration of the server/node with the ‘Server preferences’ dialog will no longer apply the changesNote that at every software update you will need to carry out this operation.We’ll see how disabling of the client can be made better.
Can you tell us the following:
– NoMachine product and version on local machine, and also on the remote nodes (Workstation, Terminal Server Node etc. You mentioned only Cloud Server on the main server.
– Whether the problem arises connecting to a physical or a virtual display.
– Specific local OS version
– Os on the remote server and nodes. If Linux, desktop version (GNOME, KDE, etc) on client and on server.Additionally the logs would be useful. You can extract using the following instructions:
If you are using Terminal Server, Enterprise Server or Cloud Server, you have Profiles available:
https://www.nomachine.com/DT09K00058#3.4.
https://www.nomachine.com/DT09K00058#4.1.
Profiles can be for:
–system
–user USERNAME
–guest
–node NODE
–group GROUPMore information is in the Administrator’s Guide linked above.
For example, nxserver –ruleadd –class session –type shadow –value no –group groupname
I’m sorry you found an alternative for your terminal server solution. I don’t think it’s because NoMachine doesn’t fit your needs. I think what you are looking for is a free terminal server, not Small Business Server, aimed at organizations, which is the NoMachine product you are referring to.
I understand where you’re coming from, and your suggestions are valid proposals. Two buttons, though, is not possible because we need the space for another button (in a future version). There is actually a dropdown box which appears with a long key press. Changing how that menu is visualized would mean changing it for all other buttons which have menus activated with long key presses, and in some of those cases having a menu appear immediately would interfere with what’s below it all the time. The UI you see is the result of a lot of painstaking design and thought, and it’s not so easy to change things overnight, but we will put our thinking caps on 🙂
Would a brief guide be useful for your users? We can certainly add one and then you can point your users to it.Another solution could be to disable desktop sharing if your users only need access to their own sessions. You can do this in profiles. This won’t disactivate the button, but regardless of whether they are enticed to clicking “My desktops” or not, they will only ever see their own.