Session negotiation failed. Cannot connect to the requested session

[jul]

Hello,

We are seeing the specified issue on our environment. We use NoMachine on Windows 10 laptops to connect to Ubuntu 20.04 VMs.

Behavior: This error comes randomly when users try to reconnect to their session. There is no visible pattern in behavior and it happens only while connecting to some Ubuntu VMs (all the VMs come from a base template, some users had it modified but we don’t see a consistency in the error among VMs with the same configuration).

NoMachine versions on the server and client-side are updated.

After adding the username in the server.confg file, we saw a reduction in the frequency of the error but it picked up again recently. Some users are experiencing it several times a day, some once a day, some once a week and others never.

We collected all the meaningful logs.

Please let me know if you can help.

Thank you.

Jul

[Carin]

Hi @jul,

Can you send us the logs you’ve collected, so that we can queue for investigation? Please send them directly to forum[at]nomachine[dot]com, adding the title of the topic to the email subject. Thanks!

[og00r]

Could you check if process nxserver –daemon is dying every time when problem appears? (check with ps -ef | grep nxserver, if new pid is up error).

We will need nxserver –daemon logs, because problem is probably on that process. Is it possible to enable logs before gathering? ( https://knowledgebase.nomachine.com/DT10O00163 )

Also what means “After adding the username in the server.confg file”, where exactly and how you add them?

[Author]

Posts