Forum Replies Created
-
Posts
-
Hello MastaG,
Thank you for the logs; having reviewed them, we would like you to:
enable the logs in node configuration file (node.cfg),
restart the nxserver,
reproduce the problem,
and then share .nx from home dir of user on server side.
using nxserver –debug enable, nxserver –debug –collect should help to create the package with logs.
As previously, please send us the logs by email.
Thank you!
Hello BlueNGray,
Your description indeed lets us think that it is a problem with the drivers, but we can’t be sure. Can you tell us if the AMD processor is on the Windows machine (the client) or the Debian one (the server)?
We suggest to try to disable hardware decoding on the client, and please also show us the CPU usage on client and server.
Looking forward to your answer.
Hello madmalkav,
Unfortunately we are still unable to understand why it doesn’t work. In order to invesigate further, can you please send us a new set of logs (server and client) to forum[at]nomachine[dot]com, making sure to reference the topic in subject ?
If needed, here’s the procedure to collect NoMachine logs: https://knowledgebase.nomachine.com/DT11R00181
Hi dlfuller,
Thank you for your message.
Can you please let me us the version you are currently using, and clarify your sentence “Also there are no graphical details for NoMachine as an application in the new 22.04.1.”.
Thank you!
Hello sunsak,
Please check the following tutorial, it should help you: https://www.nomachine.com/disabling-access-to-your-local-desktop
And let us know if you still need help 🙂
Hello ObliteRon,
I’m sending you a package for debugging via email. Please check your inbox
Thanks for your input 🙂
Hello favorite1,
We need to investigate further to be able to help you.
Please enable debug log level as explained here: https://knowledgebase.nomachine.com/DT11R00182
Once done, reproduce the problem, collect the logs and send them to forum[at]nomachine[dot]com, with the topic as reference in the subject field.
Thanks!
Hi sam302psu,
Similarly to what we asked to the other participant, we would like to check the .nx folder permissions.
Please submit this information (2 screenshots) via email to us (to forum[at]nomachine[dot]com, with the topic as reference in subject) because there could be sensitive information included:
– Open Windows explorer (file browser window)
– Type %USERPROFILE% in the URL bar
– Open View menu and check “Hidden items” box
– Right click the folder “.nx” and select Properties
– Get a screenshot of the Security tab
– Enter “.nx” folder and do the same for the folder “config”Furthermore, please tell us what is the path visible in the file browser when you enter the .nx folder.
Thank you
Hello @skibbidypaps and @PB,
We sent you both an email with a debug package.
Please check your mailboxes and follow the instructions.
Thanks!
Hello McVitas,
Unfortunately the logs you sent us do not help the investigation: there are no logs from any recent session, which can be due to a problem while gathering the logs.
Can you please send us a new set of logs (to forum[at]nomachine[dot]com, making sure to reference the topic in subject) ?
I suggest to check the procedure to collect NoMachine logs, it might be useful: https://knowledgebase.nomachine.com/DT11R00181
Hi Andre,
One of the features of NoMachine Terminal Server family (if needed, see the comparison here: NoMachine – Comparison terminal server products ) is to be able to start a virtual session that is not attached to the display and will be not visible in XEN console.
Please check the following link to know how to proceed: NoMachine – Creating new virtual desktop sessions
Let us know if you need more help.
Hello morphin,
Yes, it’s possible to use SOCKS proxy in the connection file; however in version 7.X, the connection file has to be eddied manually.
The following values have to be set:
<option key=”Enable HTTP proxy” value=”true” />
<option key=”HTTP proxy host” value=”hostname” />
<option key=”HTTP proxy port” value=”8080″ />
<option key=”HTTP proxy password” value=”password” />
<option key=”HTTP proxy username” value=”username” />
<option key=”Remember HTTP proxy password” value=”false” />
<option key=”Manual proxy configuration type” value=”socks” />
<option key=”Proxy configuration mode” value=”manual” />
In the upcoming version 8.X, it will be possible to set all these fields in the GUI.
Please let us know if this answer helps you!
Hello JooVoo,
I’m afraid a made a mistake in my previous post; I thought that the feature request I mentioned is already implemented, but it is actually not. Our developers took this opportunity to rework the content of such Feature Request and split it into two features since it was about two different aspects of rendering, the rendering of the session (of the remote desktop) and the rendering of the UI of the session.
At the moment unfortunately there is no workaround, to solve the “blurry” problem it is necessary to implement these Feature Requests:
NoMachine – Adding an option to make the session “DPI Aware” – Knowledge Base
NoMachine – Making the NoMachine User Interface “DPI Aware” on Windows – Knowledge Base
Hello morphin,
There is no way to include arbitrary data into first part of connections. However if you don’t want to use HTTP proxy a SOCKS proxy can be a good alternative, since it works with TCP connections.
Please refer to the following links:
SOCKS Proxy Primer: What Is SOCKs5 and Why Should You Use It? (securityintelligence.com)
Hello morphin,
I am not sure of the product you are using, but did you try NoMachine Cloud Server ?
Indeed it can act as some kind of proxy for the NX connections: NoMachine – Secure remote access and reliable desktop delivery across any data center or cloud
You can download an evaluation version of the software to test it.