Forum Replies Created
-
AuthorPosts
-
sziebadamParticipant
Hello!
Today I started with two attempts to connect from the Win10 machine to the XP one.
Both times I got _Connection reset by peer_ errors.
versions:
Win10 – NoMachine 7.6.2
XP – NoMachine 7.7.4
For the third attempt I updated the Win10 machine to version 7.7.4, 64 bit.
Same error.
Between attempt 2 and 3 I successfully connected from the XP machine to the Win10 one
Thus the problem persist to one direction only.
I attached a pile of logs and settings files and a screen recording of the problem.
Thanks for this great application!
I would be very thankful if this problem would get solved.
Regards,
Ádám Szieberth
File size too big to be uploaded to the Forum:
https://drive.google.com/file/d/1p6uF83_ivi3UA-neEqMo6SDibxABlrPW/view?usp=sharing
sziebadamParticipantSure, I will do it once I am back to office. I had a medical treatment and I am uncertain whether I will go there within this or the upcoming 1-2 weeks. Please be patient.
sziebadamParticipantHello!
I have the same problem when trying to connect to an XP server with a Win 10 client. The server has a legacy bundled software which I want to be able to use from the new workstations.
Once the client passes the login step, insted of seeing the server’s desktop, it got dropped with Connection reset by peer error message. I attached the server nx folder. The log was made after a fresh installation. The server was up and running without errors. I tried to connect twice, that is in the logs. I was not waited the 5 attempts at client side but closed the window after first error in both times.
Seeing the logs it seems there is some problem of reaching the node files. Log error complains file does not exist but it does. The issue might get caused that the server PC uses CP1250 codepage (or CP1252) and the username contains both space and accents.
Looking forward to some help with the issue.
Thanks in advance,
Ádám
Attachments:
-
AuthorPosts