Error 108: Connection reset by peer

Forum / NoMachine for Windows / Error 108: Connection reset by peer

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #53930
    dorkvader
    Participant

    Receiving an error 108 when attempting to connect to a Windows 2022 Server, client machine and server both have the same version of NoMachine (Version 9.1.24). I also attempted to connect to the server from another computer I had, but received the same error.

    I am able to connect to that other computer successfully, and I receive no errors, so only that server is having issues when I try to connect.

    I grabbed some logs during the connection, the connection logs, and I enabled the debug mode on the server and tried connecting as well and collected logs for that. Not sure what else could be causing this problem, maybe permissions?

    #54023
    Britgirl
    Keymaster

    Hi,  can you do a reboot of the Windows machine? After which, enable debug (Settings > Server > Security>scroll to bottom and select debug level, restart the nxserver, reproduce the error, and take new logs? Full instructions for extracting logs using the UI are available here: https://kb.nomachine.com/DT08U00298#1.  You can attach everything here or send direct to forum[at]nomachine[dot]com. Thanks!

    #54028
    dorkvader
    Participant

    I rebooted the machine, enabled Debug mode for logging. I captured some new logs on the server of the issues, I will attach the ZIP folder below for these. Let me know if this provides any further information.

    #54049
    Guro
    Contributor

    Please check the Windows event viewer in the Application and System section. The events we are interested in are those which start with nx*, in particular nxexec.exe, nxservice.exe, nxserver.exe, nxlsa.dll.

    You can use the following powershell command:

    Get-WinEvent -LogName Application -FilterXPath “*[System[(EventID=1000 or EventID=1026 or EventID=1002)]]” -MaxEvents 500

    to search faster and scan output data on nx* apps present.

    Can you export this output and send us the file?

    Thanks

    #54090
    dorkvader
    Participant

    I used that command, I will attach the output for these events below. This is for event IDs 1000, 1002, and 1026. Let me know if I need to collect any further logs, this is the logs from the server machine.

    #54094
    Guro
    Contributor

    Hello,

    It’s a bit strange as no any issue relates to the nx processes.

    Please try the following commands, maybe it will show some NoMachine related processes errors :

    Get-WinEvent -LogName “Application” | Where-Object { $_.LevelDisplayName -eq “Error” -and $_.Message -like “*nx*“}

    Get-WinEvent -LogName “System” | Where-Object { $_.LevelDisplayName -eq “Error” -and $_.Message -like “*nx*“}

    thanks

    #54105
    dorkvader
    Participant

    I ran those commands, I wasn’t able to run that system command as there didn’t appear to be any errors associated with nx under that tab.

    I will attach the results of the command below.  From what I can tell, the Search Service is failing to create a default configuration for the nx user, is that something that could be causing connection issues or is this an unrelated error?

    #54133
    klapas1
    Participant

    Hi,

    Is it possible that NoMachine was installed on a domain controller?
    If so, you can check whether the user nx exists using the following commands:

    net user "nx" /domain – checks if the user exists in the domain
    net user "nx" – checks if the user exists locally or in the domain

    If the nx user is part of the domain, please install NoMachine locally on the target servers instead of the domain controller.

    Additionally, please refer to the article regarding known issues with NoMachine in Active Directory domain environments.
    https://kb.nomachine.com/AR04O00925

    Regards,

    Klaudiusz

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

You must be logged in to reply to this topic. Please login .