Connection reset by peer

[rgmorris]

Hi,

I am having a “Connection reset by peer” problem similar to that from https://forums.nomachine.com/topic/connection-reset-by-peer-3
The server is CentOS 8.3 with NoMachine-enterprise-desktop-7.1.3-1.x86_64.
The client is Debian testing with NoMachine-enterprise-client_7.1.3_1_amd64.deb.
When I attempt to connect it fails repeatedly with “Connection reset by peer”.
I can send logs, if that is helpful?

Thanks!

[Carin]

Hi rgmorris,

Yes, logs would be helpful 🙂
Can you send us logs from the client and server side, please?
Please see the following article for guidance: Collect server and client logs manually
You can send them as an attachment to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. Thanks!

[rgmorris]

Hi,

Thanks for the quick reply. I tried to email you the logs, but kept getting “Message size violation” (the attachment was below 1MB).

So instead I sent you a link to where you can download the logs, hope this is ok.

 

[Carin]

Hi rgmorris,

Thank you! We received the logs. We will investigate and provide some feedback soon.

[rgmorris]

Hello,

Have you been able to figure anything out?

Thanks.

[Mth]

Hello.

This seems different than the topic you mentioned.

In fact the logs from the agent suggest this is the issue with Wayland:

3706049 3706070 16:28:17 661.940 DrmGrabber: ERROR! DRM init failed.
3706049 3706070 16:28:17 665.154 WaylandPoller: ERROR! Grabber init failed.

We have an article to follow in this case:

https://www.nomachine.com/AR04R01083 (“Connecting to a Wayland-based desktop running in a Linux virtual machine”)

Please try the options here. I would suggest trying the “Option #2: Use EGL capture” first,
as this right now should be the most reliable way. Please note this way modifies the display manager,
so it would be necessary to restart it as pointed in the article and it may be inconvenient to do.
In this case option #1 would be the best.

/Mth

[Author]

Posts