Forum Replies Created
-
Posts
-
Hi Tamas, right now there is no API to let you do that, but it is something we would like to offer in the future. I can’t say which version right now.
Can you resubmit the logs to issues[at]nomachine[dot]com? If you are connecting to a version 4 server, we will need to check why you are not able to run a custom session (name of application by the way?) yet you can run a virtual desktop session.
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: