June 15, 2020 at 07:40 #28106butsuriboyParticipant
NoMachine Free, Remote (server) version: 6.10.12, Platform: Windows (10, to be more precise)
NoMachine Free, Local (client) version: 6.10.12, Platform: Windows (10, to be more precise)
I’m unable to connect to the “server” (another laptop) where both computers are on my home network. I set up key based authentication as per the instructions here, but truthfully, I’m having trouble even with password based authentication. When I try to connect, it gives a “Connecting to xxx” message, but ultimately gives the error message:
Could not connect to the server.
Error is 108: Connection reset by peer
Here’s the client log (session) from my most recent attempt: [extracted & attached]
And the corresponding line from the server log (ProgramData/Nomachine/var/log/nxserver.log):
2020-06-12 22:27:22 894.448 3636 NXSERVER ERROR! Authentication with ‘NX-private-key’ from host ‘192.168.1.1’ failed. Error is ‘Wrong signature’.
When I try to just use password authentication, I get the resulting error message in NoMachine:
The connection with the server was lost
For the client log (session): [extracted & attached]
And from the server log, I get:
2020-06-12 22:39:14 768.908 10256 NXSERVER WARNING! Cannot write to FD#688.
2020-06-12 22:39:14 768.908 10256 NXSERVER WARNING! Error is: 106, ‘Software caused connection abort’.
2020-06-12 22:39:14 769.839 10256 NXSERVER ERROR! Authentication with ‘NX-password’ from host ‘192.168.1.1’ failed. Error is ‘Failed to retrieve password from client’.
Any thoughts?June 16, 2020 at 16:42 #28142CatoContributor
Start NoMachine Player on your NoMachine server host and try connection to localhost. Can you successfully authenticate in such scenario with both password and private key?
Regardless of result, please gather server-side logs according to those instructions:
Send them to forum[at]nomachine[dot]com
The logs will tell us if indeed there is an issue with password/private key authentication or if there is another reason for which you can’t connect.
You must be logged in to reply to this topic.