I’m running NoMachine server 6.6.8 on Linux, and Client version 6.8.1.
This should have been solved in 6.5, but the problem is still there. Is there anything we can do to give this a higher priority?
For now we’re forced to use a workaround with a separate putty-session that handles the agent-connections. But where the nx-client is very good at transparantly renegotiating its connection after a network change (undocking the laptop, going to a meeting, …), putty just drops the connection.
If you are using Putty, you could try using the option ‘Private key’ authentication with ‘Forward authentication’ option checked, making sure that it’s in the OpenSSH format or convert it. To do that choose the key file in the PuTTYgen main window. Then go to Conversions->Export OpenSSH key to export your private key and save it.
btw, when a TR has a “due to be fixed in ” version, it indicates a target, we can’t however guarantee that the a fix will be found, and the target should change to the version that we are currently on. For some reason, that particular TR wasn’t updated to show a later target version.