Forum / NoMachine for Mac / Connection reset by peer
Tagged: connection reset by peer, error connecting, mac
- This topic has 9 replies, 3 voices, and was last updated 2 weeks, 3 days ago by gary.
-
AuthorPosts
-
November 10, 2024 at 04:35 #50665gettingairParticipant
Hello Guys,
I have a network were some devices do not need internet access for many reasons. I just started using NoMachine, which I love so far and got my self in a bit of a pickle.
I have some machines that do not need internet access. In these machines the IP is a local ip without a router entry.
NoMachine, sees the machines in the network but when I try to connect, it says it is connected but immediately tells me it got disconnected.
I can access the same machine through remote desktop or any other method but NoMachine can not connect.
Is there a way to do this? I love the simplicity of NoMachine and would love to be able to use it.
thanks
-gio
November 11, 2024 at 17:30 #50692BritgirlKeymasterHi, are these all Mac machines? It would help to know the exact OS version of the computer you are connecting from when you experience this and to which OS version you are trying to reach.
November 12, 2024 at 18:48 #50698garyParticipantHi,
I have recently started having “Connection reset by peer” errors as well. The version on both computers is 8.14.2 and they are both running Ubuntu 22.04.1 in my case. I also have an Intel MacBook Pro running macOS Sequoia 15.1 (and NoMachine 8.14.2) as the client and it was also sometimes experiencing the same error. All of my computers have internet access so not quite the same configuration as the OP but these connections all worked solidly in previous versions as I have been using NoMachine for some time.
All connections are to the physical display which are laptop screens though I have also tried external displays and had the same problem. Both of the Ubuntu computers are using Gnome.
The connections in both cases are going through my WiFi router. I’m going to move the server to ethernet and see if that makes a difference.
November 12, 2024 at 19:18 #50701BritgirlKeymasterAre you able to send us the logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. It would be useful to have both the client (step 4 in the document) not just server side logs.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
November 12, 2024 at 22:33 #50703garyParticipantI’ve sent the log files (sorry I didn’t have debug enabled on the server) and have done a few tests. I moved the computer to connect it to ethernet and was able to connect. I then connected to a 4K external monitor and was still able to connect. Then I removed the ethernet connection and enabled WiFi and could still connect.
I left the client computer for lunch and when I returned I could not wake the server computer that I was connected to. To be clear the server computer itself was not asleep, just the display. I disconnected and on re-connect got the “Connection reset by peer” error. After collecting the logs I tried to connect again and it worked. I’m wondering if it might have to do with the display on the server going to sleep. I’ll try to do more testing and if I can get a nice reproducible case I’ll update you.
November 13, 2024 at 00:53 #50704garyParticipantI did some further testing and the problem does seem to be with the Privacy…Blank Screen Delay setting. When the screen blanks (and there is no screen lock) I get the error from both the Mac and Ubuntu client. As soon as I wake the server screen I can connect from both Mac and Ubuntu.
One other note – the correct Ubuntu version on both client and server is 22.04.5.
November 14, 2024 at 09:50 #50727BritgirlKeymasterGary, you did not submit the logs from the server side, i.e the Ubuntu machine. Enable debug on the Ubuntu machine, reproduce the problem, then gather the logs (https://kb.nomachine.com/DT07S00243).
Journalctl logs would be helpful as well.
November 14, 2024 at 19:04 #50746garyParticipantDebug and journalctl logs sent.
-Gary
November 19, 2024 at 12:31 #50799BritgirlKeymasterThanks for submitting them. Unfortunately the logs were incomplete. Please do the following:
1) make sure ‘SessionLogClean 0’ is set in /usr/NX/etc/node.cfg
2) restart nxserver
3) reproduce the problem
4) manually create an archive of the /home/base/.nx dir on the server
November 20, 2024 at 22:45 #50835garyParticipantI’ve been attempting to reproduce but now it is working. I don’t know what might have changed other than the OS does automatic updates. That seems unlikely to fix an issue like this.
If I can reproduce I will send additional logs.
-
AuthorPosts
You must be logged in to reply to this topic. Please login here.