Error 108: Connection reset by peer

[dorkvader]

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?

Attachments:

1. Servername-Windows-Server-2022-logs-2025-07-24-14.11.09.zip
2. NoMachine-log.zip

[Britgirl]

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!

[dorkvader]

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.

Attachments:

1. Server-logs-2025-08-09-13.30.56.zip

[Guro]

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

[dorkvader]

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.

Attachments:

1. NXEvents-8-13-25.csv

[Guro]

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

[dorkvader]

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?

Attachments:

1. EventViewerNXApps.csv

[klapas1]

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

[dorkvader]

Hi, I ran those commands, it looks like the nx user exists in the domain as well as locally on the computer. I believe I had installed NoMachine locally onto the machine since I just went to the website and downloaded/installed the client, unless there is another way to install this locally for AD Servers?

[dorkvader]

I just wanted to bump this, also I should mention that during installation of NoMachine, it fails to install the home directory for the NX user. Could this possibly be causing some sort of issue with the connection?

I just noticed this the last time I attempted a reinstall of NoMachine on the AD Server, it should be installing locally to the machine as well.

[klapas1]

Hi,

Thank you for the update. Given that the nx user exists both locally and in the domain, the best course of action is to uninstall NoMachine from the domain controller.

1. Uninstall NoMachine from the domain controller.
2. Verify that the nx user account has been removed from the domain using commands that I sent you before.
3. Install NoMachine locally on your target servers instead.

This ensures that the application is running on the appropriate machines without impacting your domain services.

Regards,

Klaudiusz

[Guro]

Hello dorkvader,

In reply to your last message, When NoMachine (server) is installed on an Active Directory Domain controller, the nxserver doesn’t start when the machine is rebooted. A symptom of this is that the !M icon is not present in the system tray.

This problem occurs when the nxservice starts before the Active Domain controller service and therefore NoMachine is unable to correctly impersonate the nx user.

To avoid that nxservice is started before the AD service
1)open the registry editor as administrator (redegit.exe in Power Shell). 2) Find this key:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nxservice
3) and add the following string key:
Name: DependOnService
Value: NTDS
4)Save and restart windows.

[Author]

Posts