Connection Reset by Peer (Raspberry Pi 4B)

[rempfer]

I am getting ‘Connection Reset by Peer’ from a Windows client when trying to connect to Raspberry Pi, running Raspian OS, on the same LAN.

Note: I did already try disabling USB on the Windows 10 NoMachine client.

NoMachine version on Raspberry Pi 4B: 9.0.188 (Linux).

NoMachine version on Windows 10: 8.16.1 (Windows)

From another post, it was suggested to updated the contents of /home/{user}/.nx, and so I have attached it.

Any help would be appreciated — thank you.

— Dick R.

Attachments:

1. server.log_.7z

[fra81]

Hi Dick,

your issue looks like this Trouble Report:

https://kb.nomachine.com/TR10U11031

For now, you can disable Wayland as a workaround.

[rempfer]

The Wayland option recommended was already set.

Actually I don’t even connect to RaspberryPi 400b:

“A connection timeout has occurred while trying to connect to ‘10.92.205.1’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.”

I can connect successfully with [remove], however.

Thanks for the help,

Dick Rempfer

[Britgirl]

You have two options:

– if you want to connect using the public IP of the remote host, follow the instructions in this article: https://kb.nomachine.com/AR04S01122. It is likely you need to enable port-forwarding.

– if you are unable to connect because the remote server does not have a public IP, it’s not accessible from outside its network, or you are unable to configure port-forwarding, try NoMachine Network, https://www.nomachine.com/network. You connect with the server’s Machine Id instead of its IP address. First add it to NoMachine Network to obtain its Machine Id, then use that to connect from your Player (login first). If you want to give it a try, contact us through the Contact Request form.

[rempfer]

It’s not a remote host.  The Raspberry Pi is on the same LAN subnet as the PC attempting a connection.  Somehow NoMachine not behaving on Raspbian the same way it does with other Linux distros.

I’ll keep playing with it.

Thank you, Britgirl.

— Dick Rempfer

[rempfer]

Add’l info:  Firewall is disabled on the Raspberry Pi, so port 4000 udp should go thru.

[Britgirl]

You say it’s on the same LAN, so are you using an MDNS connection (a NoMachine host broadcast on LAN) ?

Can we see the logs from the Raspberry server? Go to Settings > Server > Security, set log level to 9, reproduce the problem, then “take logs “. For full instructions see this document:  https://kb.nomachine.com/DT08U00298. Send us the complete file, you can either attach here or send directly to forum[at]nomachine[dot]com, making sure to reference the title of the topic as the subject of your email.

 

[rempfer]

The log I already sent is not sufficient?

I’m not trying anything unusual.  I don’t even know what “an MDNS connection” is.  As far as I know, NoMachine defaults to an NX/port 4000 connection-type.  That’s what I’m using.  Please check the log I already sent.  If it is NOT what you want, I will run the experiment again with Settings > Server > Security, set log level to 9.

I do thank you for your help and am not trying to be difficult (although I feel somehow that I am doing just that).  Sorry.

[Britgirl]

“I don’t even know what “an MDNS connection is” – Sorry, I was asking how you are connecting, i.e are you creating a connection or are you clicking the machine icon (pipe icon) to connect.

In any case, we still need logs with debug enabled on the server because the problem you have now is different to the original “connection reset” error. Please send the server logs and the player logs as described in the document I linked previously.

[Author]

Posts