NoMachine disconnects immediately upon successful connection to remote device

[mibjt]

I am running NoMachine 8.10.1 free, on Windows 11, and had always successfully connected to various Linux and Windows PCs without a hitch. Recently, upgraded the GPU from a 1070 to a newer 7800XT. Post GPU upgrade, I’m experiencing immediate disconnections of the virtual  after successfully connecting to any remote device. The 7800XT has all the driver installed and is running well.

Attachments:

1. log.zip

[Britgirl]

Hi, can we see the player logs (the Windows machine you are connecting from)? Please see the instructions here:
https://kb.nomachine.com/DT07S00243, section “Fourth Step: Collect Client Side Logs”.

 

[mibjt]

Hi, Please find the log files attached. Thank You.

Attachments:

1. NoMachine-log-2023.12.04-10.51.28.zip

[mibjt]

I apologize. I omitted the instructions further down the walk through. Please find the NX player logs in the .nx.zip folder.

Attachments:

1. nx.zip

[mibjt]

Hi. Just to update, I happened to update my  AMD Adrenalin graphics drivers and restarted my computer and it now works. NoMachine can now connect smoothly to my devices.

[Britgirl]

HI

thanks for the updated information. So the problem was in the drivers.

In the logs we can see:

42012 45760 2023-12-04 10:50:45 913.621 Io/Io: ERROR! Descriptor FD#16628 out of range in method ‘socket’ context [A].
Error: Descriptor FD#16628 out of range in method ‘socket’ context [A].
42012 45760 2023-12-04 10:50:45 913.621 System/System: Abort called for system at 0x0000000067095f40.
42012 45760 2023-12-04 10:50:45 913.621 System/System: Error is 22, ‘Invalid argument’.
42012 45760 2023-12-04 10:50:45 913.621 System/System: ERROR! Killing the current program.

which seems to suggest a resource leak. Had you not updated the drivers already, I would have answered that disabling hardware decoding on the Windows 11 machine is the first thing to try so that we can know whether the problem is in the drivers 🙂

[dbjungle]

I also have an RX 7800 XT.  I updated my drivers to the latest, but I notice I only have the problem when using H264 client side.  No problems with the other codecs.  H264 works fine with the same server on other client computers.

[dbjungle]

Here is also a client side log from my most recent attempt.

Server:  EndeavourOS (Archlinux) Galileo | Kernel 6.6.5 | KDE Plasma 5.27.10 | NoMachine 8.10.1 forcing H264
Client:  Windows 11 22H2 22621.2715 | NoMachine 8.10.1

The server is a virtual machine running on Proxmox.  Connecting to a virtual display.

The problem happens with H264.  Other Linux based clients are working as expected, but I do not have another Windows client to test with.  Using MJPEG or VP8 works as expected.

Attachments:

1. H264-attempt.zip

[Britgirl]

There must be a bug in latest drivers that causes a resource leak. Until it is fixed by AMD or unless you downgrade the drivers, you can only disable HW decoding in NoMachine.

[Author]

Posts