kroy

[kroy]

Can you check if the problem still exists with activated “Grab the keyboard input” option (you can find it in the nxplayer options – in the “Input” section https://www.nomachine.com/DT11M00106#2.1)? Does the issue show during connection from Debian to Ubuntu physical desktop? What desktop environment is installed on the affected machines?

[kroy]

Are you using headless system or you tried to run the application inside physical session? Which exact application are you trying to run?

[kroy]

If you have double router configuration the only way to use NoMachine at this moment is to set up separate port forwarding rules on both devices. When we release NoMachine Network this won’t be necessary. It’s our Feature Request https://www.nomachine.com/FR07J02731 you can sign up to the ‘notify me’ in order to know when it has been implemented.

[kroy]

We couldn’t reproduce problem on the same OS. Are you using native firewall? Can you show us your firewall rules? Please paste here output from sudo iptables-save command.

[kroy]

Firstly, to ensure that NoMachine users can connect to the remote desktop, they need to have a system account. If the screen is locked (so showing the local log in page), the user will be able to connect. If there is someone already logged in, the user will connect and see the screen in use.

If you want that some users could have possibility to connect without permission of desktop owner you can sign them as “trusted”. To do that open command-line as administrator. Navigate to bin folder in the installation directory (on Windows in default there is: c:\Program Files (x86)\NoMachine\) and execute command for every user you want:
nxserver --useradd <enter_username_here> --trusted physical.

[kroy]

Thanks for the report. We will take a closer look to this issue. It’s appears on specific distribution. Is that a Ubuntu Mate? It seems that the wrong command to create session is called.

So for the workaround you should change DefaultDesktopCommand key in the node configuration key to “/usr/bin/mate-session” (in case you use Mate). So open mentioned file sudo vi /usr/NX/etc/node.cfg, then comment old DefaultDesktopCommand key by adding # sign on line beginning and create new line below with DefaultDesktopCommand "/usr/bin/mate-session". After restart nxserver (sudo /usr/NX/bin/nxserver --restart) you should be able to create session.

[kroy]

You don’t need to change rules manually on native firewall on openSUSE 42.2. You don’t need set your router either provided it accepts UPnP or NAT-PMP commands. In that case your IP and port, which you can use to connect over the internet, should be listed on NoMachine’s Welcome Screen page. Otherwise you need to configure the router manually to pass traffic to port 4000 (NX protocol), 22 (SSH protocol). More information about firewall or router settings you can find in the article: https://www.nomachine.com/AR11L00827.

[kroy]

We will look closely at this problem. Does the issue show up just after NoMachine upgrade? What kind of multi-factor authentication are you using exactly? Can you send logs with debug from server side to forum[at]nomachine[dot]com? Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.

[kroy]

Do you have some specific iptables settings? Can you show here output sudo iptables -L command?

[kroy]

Despite considerable efforts we could not reproduce such a problem. We tried also a persistent antiX2usb 32-bit OS. Are you able to send to forum[at]nomachine[dot]com the two .nxs files (both working and broken ones)?

Helpful to recognizing the problem would be knowing if your password contains special characters. If you prefer, you can send us this information privately.

Also, what language do you have set on the system?

[kroy]

From the screenshots it appears you are using the IP address (you encircled) of that machine – so you are connecting to the local host. This IP address shows how to get to this computer from another machine. Other thing – encircled IP is your external. It should be used from another network (i.e not on LAN, but over the internet).

[kroy]

We strongly recommend updating your NoMachine Workstation to 5.2.11.

We haven’t been able to reduce this problem. What Mac version do you use? Is it a virtual desktop or custom rootless session?

Are any core files generated (it should be visible in home directory or in /var/crash on your Ubuntu)? If yes – can you sent gdb output? Please also send logs from server side to forum[at]nomachine[dot]com? Instructions about collecting logs you can find there: https://www.nomachine.com/DT07M00098.

[kroy]

Can you check what is the default audio input device on your mac – “server”? You can attach here screenshot if you want. Please attach also install log file. It’s located there: “/Library/Application Support/NoMachine/var/log/nxinstall.log”.

[kroy]

We couldn’t reproduce the problem. Can you please provide more information about the environment you are working with? What is the OS and NoMachine version on both systems? Are you connecting to the physical desktop or to the virtual desktop? On what terminal/konsole does the problem show?

Can you check if you are still able to reproduce problem when AgentLegacyKeyboard key is uncommented and set to ‘1’ in the node.cfg file on server side?

[kroy]

There is “version” file located on “etc” in directory where you have installed NoMachine. You can display it for example with type: E.g

type 'C:\Program Files (x86)\NoMachine Enterprise Client\etc\version'

[Author]

Posts