Connection reset by peer

Forums / NoMachine for Windows / Connection reset by peer

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #28247

    I can connect my desk computer to my remote laptop and see its desktop but after a few seconds the page is replaced
    with a NoMachine page displaying the message “Attempting to reconnect Error was: Connection Reset by Peer”.

    It was working in early June but not now.

    I am running Win 10 Prof(Build 1909) on laptop, Win 10 Home on desktop(build 1809).
    I have tried reinstalling NoMachine (6.11.2_1 free version) on both computers and rebooting
    I have also tried an earlier version of NoMachine (6.8.1_1 free version) on both.

    All give the same message!

    Please help


    It’s difficult to say what is happening and why without seeing the logs. We would need them from both client and server sides.Please see the instructions here: Submit both sets to forum[at]nomachine[dot]com making sure you use the title of this topic as the subject of your email. Thanks!


    I have retrieved the server log but am having trouble getting the client’s log. I don’t understand the instruction:

    “Collecting client side logs manually requires to make the following operations on the user’s computer from which the connection is started:”

    Is the “user’s computer” the client or the server? I assumed it was the server and looked on the client for the /.nx directory but couldn’t find it.

    – Patrick


    The client-side logs refer to the machine that you are connecting from, the device where you initiate the NoMachine connection. The server-side logs refer to the computer or host you are connecting to.

    Please send them to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email. Thanks 🙂


    I have attached what I hope are the correct folders.

    I could not find the nxtrace.log file but included the client .nx folder anyway.

    –  Patrick

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.