Forum / NoMachine for Windows / How to resolve “Session negotiation failed”
- This topic has 1 reply, 2 voices, and was last updated 2 years, 10 months ago by Cato.
-
AuthorPosts
-
December 23, 2021 at 11:09 #36805JMillerParticipant
I have NoMachine as a backup way to my remote computers, but today when I actually need it, it is failing with “Session negotiation failed”.
I have already read this post: https://forums.nomachine.com/topic/session-negotiation-failed-on-windows-11 but it does not work in my case, since the account is already password-protected.
Both client and the server are running NoMachine 7.7.4 with Windows 10 21H2
Authentication method: Key based authentication
This is the log from server side (nxserver):
10516 10516 2021-12-23 02:03:28 418.311 NXSERVER ERROR! Encryptor context not received.
2868 2868 2021-12-23 02:03:33 268.948 NXSERVER User ‘<USERNAME>’ logged in from ‘<ClientIPv6>’ using authentication method NX-private-key.
2868 2868 2021-12-23 02:03:38 808.972 NXSERVER ERROR! Cannot connect to local node.
2868 2868 2021-12-23 02:03:38 814.980 NXSERVER WARNING! Process ‘C:\Program Files (x86)\NoMachine\\bin\\nxexec.exe –node –user <USERNAME> –priority realtime –mode 0 –pid 1164 -H 684’ with pid ‘12848/1200’ finished with exit code 1 after 0,127 seconds.
2868 2868 2021-12-23 02:03:38 814.980 NXSERVER WARNING! NXNodeExec: nxexec with pid ‘12848’ just died with exit code ‘1’.nxerror.log
12524 3796 02:07:12 704 NXLsaSendRequest: ERROR! Cannot send request to NXLSA package.
Error code is : 0.
Package’s response is : 0xc0000001.
12524 3796 02:07:12 706 ExecuteNodeNXLsa: ERROR! NXLsa/exec failed and no password available.
12524 3796 02:07:12 721 BecomeSystem: Running as SYSTEM user.
12524 3796 02:07:12 768 ExecuteNodeToken: ERROR! Failed to create process as user.
12524 3796 02:07:12 769 ExecuteNodeToken: ERROR! Error is ‘1314’
12524 3796 02:07:12 770 nxexecExecNode: ERROR! Failed to launch node process.
12524 3796 02:07:12 771 main: ERROR! Could not execute nxnode.
Info: Connection from <ClientIPv6> port <ClientPort> closed on Thu Dec 23 02:07:12 2021.
Info: Handler with pid 10180 terminated on Thu Dec 23 02:07:12 2021.
10180 12188 02:07:12 876.794 Io/Io: WARNING! Descriptor FD#872 type socket still open at exit.
10180 12188 02:07:12 876.794 Io/Io: WARNING! Descriptor FD#1032 type socket still open at exit.Would be great if someone can assist on how to resolve the issue. Thanks!
Attachments:
December 23, 2021 at 14:02 #36810CatoParticipantHello JMiller,
It looks like an issue with missing privileges of nx user account.
Please, check this reply: https://forums.nomachine.com/topic/first-time-connecting-session-negotiation-failed-error#post-34887Let us know if enabling missing privileges and restarting nxserver solves the issue.
-
AuthorPosts
This topic was marked as solved, you can't post.