NoMachine Entreprise v9: please type in your username to login as a system user

[wernermaes]

Hello

I upgraded my NoMachine Enterprise Client to version 9 (9.0.188).

When I try to login to my Terminal Server I know get an extra screen: “Please type your username to login as a system user.”
My username is filled in and I have to click OK and the connection works.

With my v8 client I do not get this extra screen? How can I avoid this extra screen?

Kind regards

Werner Maes

Attachments:

1. 

   qnx1.png
   

[Tor]

Hi. Do you use a private key to authenticate to the server?

[thibaut]

Hi, we have the same problem and use a private key to authenticate. Is there a new flag to disable this annoying behaviour?

[wernermaes]

Hello Tor

I use a private key to authenticate.

Apparently this issue is related to an issue that the Nomachine developers are investigating. It seems to be related to the updated libssh2 package.

The current workaround:

Configure the NoMachine player to use the system SSH client:

edit $HOME/.nx/config/player.cfg and modify the value of the following key

from:

<option key=”SSH client mode” value=”library” />

to:

<option key=”SSH client mode” value=”native” />

 

[wernermaes]

This problem is related to https://kb.nomachine.com/TR06W11397

[Tor]

We’re still in process of investigating the behaviour, but of course it is not expected so there is nothing wrong on your side.

Could you please export client side logs (Settings > Security > Take logs) and send them to forum[at]nomachine[dot]com? We’re like to address this issue quickly, any hints will be helpful.

[thibaut]

Hi,

Changing ”SSH client mode” to “native” did not change anything for us. Also NoMachine directly switches it back to “library” again and updates the connection configuration file when connecting.

Thanks.

[wernermaes]

Hello Thibaut

If you edit the player.cfg file NoMachine should not change it. Are you sure that you’ve used “native” when connecting?

You can see this kind of error message in journalct logs on the server side if it fails

Jun 12 16:41:13 icts-q-nx-1 sshd[126207]: error: maximum authentication attempts exceeded for user from 2a02:… port 56194 ssh2 [preauth]

Jun 12 16:41:13 icts-q-nx-1 sshd[126207]: Disconnecting authenticating user 2a02:… port 56194: Too many authentication failures [preauth]

[Tor]

@thibaut the client mode being reverted could be caused by a client process overwriting your change, so if you want to test that, be sure to close all running nxplayer instances.

Additionally can you confirm if, like @wernermaes, you’re using the SSH protocol to connect and agent forwarding to authenticate?

[Tor]

Hey there. We’ve found the issue and documented also a workaround:

https://kb.nomachine.com/TR06W11407

The fix will be included in the next maintenance which is to be released shortly.

[thibaut]

Hi,

I can confirm that also for us, changing from “library” to “native” in player.cfg prevents the additional username popup from appearing (changing the setting worked fine on second try, closing any NoMachine process before so the setting isn’t overwritten). Authentication is working fine also with the “native” setting.

And yes, we are also using SSH as protocol to connect (with authentication via ssh agent), and we are making use of agent forwarding as well.

Thanks

[Author]

Posts