V9.0.188, server connection Error is 108: Connection reset by peer

[octopus42]

Anytime I try to connect to my remote system, I get the following error: Could not connect to the server. Error is 108: Connection reset by peer

Everything works fine when the server was v8.16.1, the latest version I had before upgrading. If I upgrade the server to the latest, whether it be an in-place upgrade or a fresh install, using Revo Uninstaller to uninstall the app on the server side, the server refuses to work. Rolling back to v8.16.1, I’m able to connect to my system remotely again. What changed in this v9 version or what changes do I need to make to my system to get v9.0.188 to work? The client-side version, whether it be v8.16.1 or v9.0.188 has no affect on a successful connection but in this instance its 9.0.188. Connecting system is win11 24h2

During my initial install, as it’s a windows server, 2025 system running AD, I did need to add the nx user to a few policies in gpo to get the service happy. Those same changes are still valid. I even deleted and readded the ‘nx’ user in the gpo local policies. I am using the free version as this is a homelab

[Britgirl]

So you can reproduce it when you connect from on Win 11 (any NM version) to NoMachine v9  on Windows Server 2025?

[octopus42]

Correct. On the server side, v9.0.188 is installed. On the server side, uninstalling v9.0.188 and reinstalling v8.16.1, my previous version, I can connect fine. Going back to v9.0.188, it stops working

[octopus42]

Bumping this. I still have this issue and just submitted logs from the server side with debug level set

[Britgirl]

Thanks for those, I was just about to come and ask you to send them. We’ll take a look and come back to you.

[Britgirl]

The logs show a possible issue with permissions. Please follow the instructions here to get further verbose logs from the server machine you are connecting to: https://kb.nomachine.com/DT08U00298#2 from the CLI. Restart the server before reproducing the issue and then resubmit. Thank you!

[octopus42]

Just resubmitted the logs. Sorry it took so long

[Britgirl]

Hi, we got the logs but strangely there were no server logs at all. In the nxd log it’s clear that a connection arrives to the server, and then finishes without any error. Maybe the logs from the client side would be useful at this point. Let’s try this way.

On the server side, go to Settings>Server>Security> scroll down to logs, and set the level to Debug. Restarting the server is requested to make change effective.

On the client side, go to Player Settings -> Security and check option ‘Don’t delete log files on exit’.

Connect to reproduce the error and then 1) click ‘Take the logs’ from the message dialog that you see, and then 2) go back to the server host and click ‘Take logs’ from the Settings>Server>Security. Restore log level 6- Standard to avoid verbose logs. Restarting the server is requested to make change effective.

Send everything by email (one attachment for the player logs, one for the server logs). Thanks!

[octopus42]

Hmm interesting. Is the server log in question the server.log found under programdata\nomachine\var\log\? If it is, the log does update, but I can only view it using notepad++ opened in admin mode. If I make a connection, notepad++ will notify me the file updated.

This really does seem like some permission issue and almost like the nx account lacks something. Is there documentation on how to install nomachine on Windows Server and what permissions the nx account needs as well as any policies needing to be set?

The AD and group policy I’m using are the same for what I had configured between v8 and v9, v9 just seems to be particular for some reason

 

[Guro]

Hello,

Could you take a look at the following article

How to restore proper permissions for nxservice on Windows
http://nomachine.com/AR04V01228

and tell us if the steps there help in restoring permissions?

Thanks

[Author]

Posts