Forum Replies Created
-
Posts
-
I also replied to the mail I received about your question, but I can also repeat it here in case my mail answer did not reach anybody:
I tried it out and left both windows open. They both freeze/crash simultaneously. And no window of the client opens again after the crash. In Windows task manager I see processes of the client being started, but no window is opening on the client desktop. The server installation on the ubuntu system is however very stable and did never crash. In the meantime I upgraded Ubuntu to 23.04. All good on the server. Only issues on the Windows client.
In the meantime I also upgraded to the latest version 8.5.3 of NoMachine client and server. It looked good and stable for a while, but also the latest version did finally show the same symptoms. I guess I was just lucky for a while.
I would not even mind that it occasionally crashes. Just restarting the client would be ok. But it is annoying that it crashes in a way that only a complete reboot of the client machine is helping to recover.
Hi Britgirl,
Thanks for your help. I started now with the software update only. I will observe how it performs and if the issue is gone with the new version. By the way, I updated the version on both, the client and server, to 8.3.1.
If this does not help, I will try your other proposals. I think hardware decode/encode is a useful feature and I only want to disable it if the new software version still shows the same problem.
By the way, the load on the GPU caused by hardware decode is quite low in my opinion. Windows task manager shows around 20-30% 3D load and 5-6% video decoding load for the Iris Xe GPU on my laptop with the NX client. I had to play a video on the shared desktop to cause a continued image change and see any sustained GPU load at all. But this is of course expected.
I think I have to observe this for some time before I declare the problem gone or not as the described problem happens only once in a while now. It is rare enough to accept it if the only thing needed would be to restart the client software. But having to reboot the entire client machine is the annoying part.
I have some testing to do now and I will report on the results.
Hi,
Thanks for your help.
I did include the logs from the .nx folder that did show successful sessions as well as those that show up after I had to kill the client and restarting the enterprise client did not produce a window. The latter ones are the very short session logs.
Please note that I recently use the server connection over an ssh tunnel with implicit forward of port 4000. The connection is therefore made to localhost:4000. If I do not use the tunnel, but direct connection, the symptoms of occasional freeze with killing the client process and then needing a reboot before a client window is available again are the same. I use the tunnel, because I also wanted to use the connection from remote, but do not want to open the server port through router port forwarding and expose it publicly. All logs attached in the mail are from sessions in my home LAN.
My use case is connecting to my home server from my work laptop.
In my setup the server is my private home server and the client is my work laptop. I suspected that the problem is related our enterprise security policies, which are allergic to incoming connection to our devices. Therefore the server component of the free Windows software is a problem. I do not need the server on the Windows system. I uninstalled NoMachine free version and downloaded and installed the Enterprise Client. From what I can see it is basically the same client, but without the integrated server. This seem to work. I did now use it for a few hours without any freezing or other strange behavior. It is actually very responsive even in higher screen resolutions.