- This topic has 5 replies, 2 voices, and was last updated 2 days ago by
.
-
Posts
-
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
So you can reproduce it when you connect from on Win 11 (any NM version) to NoMachine v9 on Windows Server 2025?
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
Bumping this. I still have this issue and just submitted logs from the server side with debug level set
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.
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!
You must be logged in to reply to this topic. Please login here.