Forum Replies Created
-
Posts
-
I doubt this is related to NoMachine, nor Google Cloud, and that the problems are still there even without NoMachine installed! Given that you mention svchost.exe process memory becomes high which is known for causing similar memory problems, try checking this article: https://www.wintips.org/how-to-fix-svchost-exe-netsvcs-memory-leak-or-high-cpu-usage-problems/
No logs were received so this topic will be closed. Please update to the latest version available on the website and let us know if this is still occurring.
Please update to the latest version of the software and let us know if this issue is still happening. In that case, open a new topic 🙂
Can you update to the latest version and see if you can replicate the behaviour? Extract the debug logs as mentioned before and resubmit.
Connect with ssh and:
sudo /etc/NX/nxserver --history | grep Connected sudo /etc/NX/nxserver --disconnect <session ID>or even:
sudo /etc/NX/nxserver --restartYou could also try connecting from another device.
Please update to the latest version. A number of issues with audio were fixed. If you continue to have problems, please start a new topic.
Hi, wow, that’s quite a distance 🙂
This could indeed be useful but of course it depends on whether the target machines respond to the ping or not. We keep track of all network data that an application like NoMachine can ever track, and so it would be a matter of how to make this data more “accessible” to the user and easier to read, and evaluating where and how to make it accessible without interfering with the design of the user-interface. These statistics, however, are at the application level (i.e what NoMachine sends and retrieves).
NoMachine proxy keeps track of the time of round trips, statistics of lost UDP frames, retransmissions, amount of key-frames requested, congestion and bitrate values calculated by the proxy and reported in proxy callbacks etc etc. The actual data about the network and a real estimate of the performance of the network can only be retrieved by analysing the OS kernel and the networking HW (network card, TCP/IP stack of the OS, traversed routers and so on).
What there is available to you already, which sysadmin and network experts will appreciate, is the Statistics section of the NoMachine connection. Please consult this article which gives guidelines on how to interpret this data: https://www.nomachine.com/AR02N00875 (we’re in the process of updating it btw)-
What you should concentrate on is the ‘link’ section which presents the information you would probably be more interested in. The X Protocol section can be ignored 🙂
This FR is available in “virtual desktop sessions” supported in the Terminal Server for Linux products. “Virtual desktop” does not refer to hypervisor technology.
But the flickering problem is still there.
Did you already consult our tips for using Jetson Nano? If not, and you are using Unity, please consider changing desktop environment.
Tips for using NoMachine on NVIDIA Jetson Nano
https://www.nomachine.com/AR02R01074Hi, I’m pleased to know the patch worked 🙂 Using an earlier version of NoMachine probably would have produced the same results, so it was just easier if we sent you a working version from the start, at least that way you can use the software again rather than wait for the next maintenance.
Why it happened…. Could it be that you had Win7 set to English and then in Win10 you chose your native French? Maybe that Win10 translates the system username?
Hello, since the most recent version is now 7.0.211, I suggest you update to this (which also fixes the TR which is linked above) and if there is any unusual behaviour, let us know by opening a new topic. Thanks! 🙂
Quoting from the article I linked to in your other topic:
“A common solution, valid for all the supported Operating Systems, is to adopt a fake display dongle (also called ‘dummy dongle’) inserted in the video card port to simulate the presence of a screen and force the system to take full advantage of the GPU as if a real monitor is connected. In case of a Linux host it’s necessary to reboot the machine or restart the display manager to make this operative.”
Check if the Jetson Nano forums on the nvidia developers forum have any other suggestions, maybe?
Thanks for alerting us to the issues you’ve been having with the forums. We’ll investigate. Just to recap, this is your second topic (the other one is about flickering and I asked you to submit the video via email because big attachments aren’t allowed and sometimes removed because of our spam filter) 🙂 However, I don’t think it will be necessary as Fra has understood what you mean.
Regarding the problems you’re having with NoMachine on Jetson Nano. For the flickering, please consult your other topic. https://forums.nomachine.com/topic/flickering-problem.
For problem number 4, please check that you have turned on the “advertize feature” in the ports panel. Disabling it on the server means that computer won’t show up in the connections panel. Check here: https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network
Check that you have not disabled seeing other users’ computers in the ‘Machines’ panel, which are being advertized on the network. This is done on the player side: the box “Don’t show other computers on the network” in the Privacy panel of the player. See this guide for more info: https://www.nomachine.com/DT10O00154#2.5. If you’re still not seeing other computers on LAN, we’ll need to know what OS computers you should be finding on the LAN and what version is installed of NoMachine.
For problem number 2, it’s related to problem number 3) and that your Jetson Nano is headless. The video cards installed do not work well on a headless set-up. This is not really the fault of NoMachine. I suggest you read this article which explains a few ways to work with headless Linux.
How to solve black screen and other possible problems on headless machines
https://www.nomachine.com/AR03P00973We can provide a patched component for you to try if you’re interested. I’ve sent you a link to the download package. Please check for emails from the forum.
I think here the issue is internal Windows system account not common system accounts (local usernames). We can provide a patched component for you to try if you’re interested. Please check for emails from us for the download link 🙂
We’ve found the cause and opened a Trouble Report.
Connecting to the Windows physical desktop is not possible when the system account name contains non-latin characters
https://www.nomachine.com/TR12R10003