Forum / NoMachine for Windows / The session negotiation failed
- This topic has 6 replies, 2 voices, and was last updated 2 years, 3 months ago by Britgirl.
-
AuthorPosts
-
July 21, 2022 at 07:31 #39374IlyaParticipant
Hello. Trying to connect to a new computer gives this error, what to do in this situation
Info: Starting NoMachine version 7.9.2.
Info: Loading settings from ‘C:/Users/andrianov.i/.nx\config\player.cfg’.
Info: Loaded translation files for ‘Russian’.
21948 21424 12:00:10 279.910 Main: Creating the client session.
21948 21424 12:00:10 279.910 ClientSession: Initializing session at 0x01ebd5d0.
21948 21424 12:00:10 404.912 ClientSession: Initialized session at 0x01ebd5d0.
21948 21424 12:00:10 407.920 ClientSession: Starting session at 0x01ebd5d0.
21948 21424 12:00:10 416.909 ClientSession: Going to start session ‘C:\Users\andrianov.i\Documents\NoMachine\Подключение к wsfrsd-bank2.nxs’.
21948 21424 12:00:10 425.915 ClientThread: Creating new thread.
21948 21424 12:00:10 430.910 Connection: Initializing connection at 0x05e5ef08.
21948 21424 12:00:10 433.908 Connection: Initialized connection at 0x05e5ef08.
21948 21424 12:00:10 433.908 Connection: Starting connection at 0x05e5ef08.
21948 21424 12:00:10 433.908 ClientDaemonConnector: Starting a new connection to host ‘ws-frsd-bank2’ on port ‘4000’.
21948 21424 12:00:10 434.909 Connection: Started connection at 0x05e5ef08.
Info: Connection to 192.1.1.89 port 4000 started at 12:00:10 442.912.
21948 21424 12:00:10 445.910 ClientSession: Started session at 0x01ebd5d0.
Info: Slave server running with pid 15604.
Info: Listening to slave connections on port 43718.
21948 21424 12:00:10 454.910 Main: Entering the GUI event loop.
21948 4576 12:00:11 075.904 ClientSession: A valid certificate for this server was found.
21948 21424 12:00:16 378.867 ClientSession: Going to query the server for available services.
21948 21424 12:00:16 503.869 ClientSession: Going to query the node for available services.
21948 21424 12:00:16 520.866 ClientSession: WARNING! Could not map the UDP port using UPnP.
21948 21424 12:00:16 520.866 ClientSession: Going to attach session at index ‘0’.
21948 21424 12:00:16 607.869 Keyboard: Current model ‘evdev’ session model ‘evdev’ layout ‘en_US’ variant ‘(empty)’ options ‘(empty)’.
21948 21424 12:00:17 039.868 Connection: Connection at 0x05e5ef08 failed.
21948 21424 12:00:17 039.868 ClientSession: Runnable at 0x05e5ef08 caused the session at 0x01ebd5d0 to fail.
21948 21424 12:00:17 039.868 ClientSession: Failing reason is ‘Отказ при согласовании сеанса.’.
21948 21424 12:00:17 042.863 ClientSession: Stopping session at 0x01ebd5d0.
Info: Slave server running with pid 3924.
Info: Listening to slave connections on port 55280.
21948 21424 12:00:17 057.863 Connection: Stopping connection at 0x05e5ef08.
21948 21424 12:00:17 057.863 ClientDaemonConnector: Stopping the current connection.
21948 21424 12:00:17 059.866 Connection: Stopped connection at 0x05e5ef08.
21948 21424 12:00:17 071.868 ClientSession: Stopped session at 0x01ebd5d0.
21948 21424 12:00:17 071.868 Connection: Stop reading because of parser request.Attachments:
July 25, 2022 at 08:44 #39418BritgirlKeymasterPlease provide more details of client OS and server-side OS. I’m also assuming you have the free version installed on both sides? Does the problem continue if you update both sides to 7.10?
July 28, 2022 at 09:24 #39480IlyaParticipantProblem continues Windows 7
July 28, 2022 at 13:45 #39488BritgirlKeymasterTo understand what is happening and why the session negotiation failed, we would need to see the server-side logs. Can you follow the instructions here and submit them to forum[at]nomachine[dot]com?
Collect server side logs automatically
https://kb.nomachine.com/DT11R00182July 28, 2022 at 14:26 #39491IlyaParticipantserver-side log
Attachments:
August 9, 2022 at 08:49 #39622IlyaParticipantWill you help me with this problem?
August 9, 2022 at 11:53 #39628BritgirlKeymasterApologies, I thought I had answered.
Your issue looks similar to another topic, and it’s related to required privileges which are missing. It appears that ‘nx’ user doesn’t hold the privilege required for starting the nxnode process. In this case, most likely ‘Act as part of the operating system’ is missing. This is the list of all privileges needed by ‘nx’ account:
– Act as part of the operating system
– Log on as a service
– Adjust memory quotas for a process
– Replace a process level tokenHere is the link to the other topic: https://forums.nomachine.com/topic/first-time-connecting-session-negotiation-failed-error#post-34887
-
AuthorPosts
This topic was marked as solved, you can't post.