July 8, 2022 at 21:40 #39140
I’m having problems with clients hanging when connecting to NXServer running on Windows 10. When clients hang, CPU usage shoots up and fans spin up on the client laptop. The NXClient/Player window becomes unresponsive and has to be killed.
I’ve tried from an Ubuntu 20.04 Linux Client as well as a Window 10 Client running in a VM on the Linux host. Full details below:
- Server: 7.10.2_8 Free Windows 10
- Client 1: 7.10.1 Free Ubuntu 20.04
- Client 2: 7.10.2 Free Windows 10 VM running on
I’ve tried disabling hardware decoding on Linux client but no change. The sequence I usually see is
- Connect from client to server
- Connection usually fails with a “Bye Message” error
- Connection keeps retrying then eventually connects
- I get a blank white screen
- Going to settings such as display settings results in hang
- Sometimes I do not get the error from 2 above and it goes straight to blank screen and hangs.
It seems some problem on the server is triggering a hang on clients. Once the hang happens I have to kill all nxclient and nxplayer processes to recover.
Attachments:July 11, 2022 at 16:26 #39181
I was able to narrow this problem down to a faulty USB to ethernet adapter on the client machine. It seems the adapter has problems with high throughput. This also explains problems I’ve experienced with remote desktop and [removed] connections. [removed] would mostly work with low quality settings. However, I would not expect the NX client to hang and require the user to kill the process.
Let me know if there is anything I can do to diagnose the client hang.July 11, 2022 at 17:58 #39185BritgirlKeymaster
Hi, it’s certainly not something we’ve seen during tests and very unusual. We’re not quite sure how NoMachine client hanging could be related to high throughput on the affected device, so logs from the affected client Linux device would be useful in this case.
You should make sure the check box “Don’t delete logs on exit” is ticked in the Player settings -> Security panel, and then reproduce the problem. Detailed instructions on how to gather the client-side logs are available here: https://kb.nomachine.com/DT11R00181#2. Please send them directly to forum[at]nomachine[dot]com making sure to reference the topic title in the subject of your email. Thanks!July 11, 2022 at 21:01 #39186
The USB to ethernet adapter appears to have a hardware problem or the drivers are buggy since I see a number of errors in the kernel log. It should be noted that the Windows client also hangs in the same manner. It is running on a VM on the Linux host and is bridging to the same faulty interface.
I switched the connection to use a different ethernet adapter and everything works fine now. I’m not sure why the client hangs but I will grab the logs when I have a chance.August 5, 2022 at 15:54 #39586BritgirlKeymaster
The logs would be useful. We will keep this topic open for a few more weeks. When you get a chance to submit the logs, please attach them here or send directly to forum[at]nomachine[dot]com.
You must be logged in to reply to this topic.