Forum / NoMachine for Windows / Was working but now getting Error: Connection reset by peer
Tagged: cant connect, windows
- This topic has 6 replies, 3 voices, and was last updated 3 months, 1 week ago by Britgirl.
-
AuthorPosts
-
June 11, 2024 at 08:34 #48456PhilipKParticipant
Hi NX,
Thank you for your amazing tool you’ve created and graciously given to the community!
I hope you can be of some assistance, as my setup stopped working recently!
I used to connect to a client from a virtual machine, but suddenly after a weekend I can no longer connect to the client.
It shows the pop ups that I’m connected but mine never connects, only going to Connection reset by peer, and then starting over. At this time it also flashes the screen on the Host.
I can gather anything you want, just send me some links to knowledge bases and I’ll get right on that 🙂
NoMachine free version – version 8.11.3
Virtual machine is Windows Server 2022 running the Client and Host is running Windows 10.
UT22 zip is logs from the Virtual machine used as Client, the NoMachine zip file is a debug collection from the Host system
Kind regards,
Philip K.
June 11, 2024 at 15:03 #48463BritgirlKeymasterHi, logs suggest a possible network issue in that both client and server sides record a disconnection. However, the logs don’t match i.e it appears you took them at different times. So to be extra sure, we need you to submit new logs. Clean out old logs, reproduce the problem and then submit the new client and server logs like last time 🙂
Also useful, the output of
nxserver --status
run in a Windows CMD prompt on the Windows server you are connecting to would be useful as well. Open the CMD console as administrator and input"c:\Users\All Users\NoMachine\nxserver\nxserver.exe" --status
. Paste the output here.June 11, 2024 at 16:00 #48464GuroContributorPlease open powershell on the server side as admin and run the following command:
get-childitem \\.\pipe\
and provide all lines which contain pipe name as nx*August 6, 2024 at 10:49 #49079PhilipKParticipantHi Britgirl,
It takes a little while to navigate the Server in question, but I believe I managed to enable debug logging and reproduce the error quite, and saved the logs rather close to each other. Zipped up the .nx folder of the Client and /var/log directory on the server.
nxserver –status result attached as screenshot
@Guro I ran this and there were around 4 lines in the same area, but I managed to not get a screenshot of the lines. I did not see anything useful displayed as the information in the other rows were the same outside of the long UID after the nx* lines.
Please let me know if this is a solid direction to move in!August 6, 2024 at 16:22 #49094BritgirlKeymasterCan you send those logs directly to forum[at]nomachine[dot]com? Please use the title of this topic as the subject of your email. Thanks.
August 9, 2024 at 17:26 #49128BritgirlKeymasterJust to let you know we received the logs and will come back to you once developers have finished their analysis.
August 12, 2024 at 09:57 #49140BritgirlKeymasterThere are logs missing from the server side from user’s homedir/.nx. Additionally, you are using 8.11. It would be useful to update to 8.12 and get fresh logs with debug enabled. Make sure you zip up the entire .nx from the NoMachine Windows host you’re connecting to. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243.
Edit 10/10/24 – no new logs were received. We suggest to update to the latest 8.14 and if you continue to have issues, open a new topic with the full logs attached.
-
AuthorPosts
This topic was marked as closed, you can't post.