Britgirl

[Britgirl]

This looks similar to a known issue

Sudden termination of Cinnamon desktop when the popup ‘desktop is viewed’ is present
https://kb.nomachine.com/TR08U10994

The workaround (follow the link to see the complete description) is open the UI  on the Mint machine -> Settings -> Server -> Security -> section ‘Desktop Notifications’ and uncheck option ‘Show that the desktop is viewed when somebody connects’.

[Britgirl]

Hi,

is NoMachine installed on the OS of the physical hardware or is it running in the virtual machines (which I understand to be Windows and Ubuntu)?

When you go into the control panel of the OS of each of the VM, what resolutions do you see?

If you go in to the control panel of the OS of the physical host, what resolutions do you see?

How are you using RDP to connect? Are you using it to connect to the VM or to the OS of the server?

 

[Britgirl]

What version are you using? This looks like the same bug as this report: https://kb.nomachine.com/TR10T10648, fixed in an earlier version. We are not able to reproduce it on 8.9.

[Britgirl]

Hi,

first thing to try is disabling hardware decoding on the computer you are connecting from.

Exit the Player and then go to $HOME/.nx/config/player.cfg on your machine, edit the “Enable hardware accelerated decoding” key and set the appropriate value as indicated to ‘disabled’. More about this is in following article:  https://kb.nomachine.com/AR07U01202

If that doesn’t help, send us:

– nxplayer logs
– journalctl output (sudo journalctl -x |grep -i gdm)
– /var/log/Xorg.0.log.old (cat /var/log/Xorg.0.log)
– if there is a core file from nxplayer, extract the backtrace

Instructions are how to extract player logs are available in section 2. How to Collect Client Logs from Users’ Devices of the following article: https://kb.nomachine.com/DT07S00244. That article also outlines how to extract the backtrace (section 4).
Send everything to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks!

[Britgirl]

The NoMachine icon represents the NoMachine service i.e that there is a daemon running and that the server is either running or temporarily stopped. If you “shut down” the server (from NoMachine settings)  or “quit the service” from the !M icon, the !M icon will disappear, and you will have to open the program from the applications menu, go in to server settings and “start the server”.

Notifications appear from that icon. You will have noticed that when you connect, the message “User xyx is connected” pops up. And if someone is connected to your desktop in desktop sharing, a “desktop is viewed” message appears. More about the !M icon in the system tray can be found here in the dedicated document: https://kb.nomachine.com/DT07S00239.

If I access the Linux machine directly the NoMachine server GUI reports that the NM server is active, but the NM icon can take a few minutes to appear, if it appears at all.

This is what needs investigating. That icon should be visible/accessible permanently if the service is running. It should not be appearing/disappearing. If it is slow to appear, again, this is not normal. We’ll wait for the logs, they will shed some light on what is happening. Your other topic contains the link to the instructions on how to enable them.

Is the Ubuntu installation running Wayland? If you switch to X.org, do you see the same behaviour?

[Britgirl]

The screenshot is the expected dialog, so you followed the instructions correctly 🙂 It is using a key, and the client is asking for the passphrase of that private key. Is this not what you wanted?

[Britgirl]

Thanks for letting us know. It will be useful for other Avid users, I’m sure.

[Britgirl]

Can I ask what version of NoMachine you were running before you updated it? You need to configure the server settings of the machine you want to connect to accept connection requests – without asking for desktop owner’s authorization. This was also configurable in v7 and it’s likely that you set it to not ask the owner, but there was a change in the name of the key. You should check that in your server.cfg there is the key “PhysicalDesktopAccessNoAcceptance”. Can you tell what its values are or attach the cfg file here?

Another thing you should can is the user name which you are logging in with. As the owner, the popup doesn’t show, but if you connect as a user which is not the owner, i.e another system user, the popup will show.

To disable requesting for the owner’s authorization before connecting to the desktop do the following on the server side:

– Open the NoMachine User Interface from Programs menu or Applications.
– Access the Server settings
– Open the Security panel.
– Go to User Acceptance and make sure that the box “Don’t require acceptance if the user logged in as a system user” is enabled.

Does this help? 🙂

[Britgirl]

Try resetting Permissions for Accessibilty and Screen Recording. Remove NoMachine from both lists (click the ‘-‘ button) and then restart NoMachine (you can do it from terminal with sudo /etc/NX/nxserver --restart) and follow the prompts that should direct you to enabling permissions again.

[Britgirl]

This is strange behaviour and not one that we are aware. If you send us the logs that we requested in your other topic, we can check if there is anything that indicates why the nxserver is not starting.

NoMachine defaulting to headless rather than “real” desktop

[Britgirl]

We are not able to reproduce this behaviour connecting from Windows to Debian Buster, 8.9 both sides.

What desktop environment are you connecting to exactly?

What do you mean with “If I plug the keyboard directly into the client – it works correctly as it does when I plug it into the host. When I type into the client the keys are translated at the host.” Is this a laptop? So you are plugging in an external keyboard and it works, but when using the device’s own keyboard, you get alternating case text?

Does this happen in all applications?

[Britgirl]

Apologies for the incorrect link, now corrected and repasted here:
https://kb.nomachine.com/DT07S00243

Please use the instructions in this document and not the document you found which is for an old version of NoMachine and does not apply to you. I have pasted the first step here for your convenience.

First Step: Enable Debug Level on the Problematic Server/Node Host
(macOS)

Open a terminal on your mac machinee and run:

$ sudo /etc/NX/nxserver --debug --enable all

then continue with steps in the document. You can send everything to forum[at]nomachine[dot]com. Please use the title of the topic as the subject of your email. Thanks.

[Britgirl]

Hi,

what version of Fail2Ban are you using? We have an article that outlines how to configure Fail2Ban with NoMachine which you can consult here: https://kb.nomachine.com/AR05P00983. These changes apply to the latest version of NoMachine, currently 8.9.

We just updated it to include the change required for Fail2Ban 1.0.2 or later, which are reported below.

For Fail2Ban v1.0.2 and later, the following changes need to be made:

———-
sudo cat /usr/NX/share/fail2ban/nxauth.conf
———-
#
# Fail2Ban filter for NoMachine.
#

[Definition]

#
# The default regex matches all the supported authentication methods
# for connections by NX protocol, which are:
# password   : Password authentication.
# private-key: Key-based authentication.
# kerberos   : Kerberos ticket-based authentication.
#
# For example, set the regex to match password based authentication
# method:
#
# method=password
#
# Most common error messages:
#
# Method: password
# ErrorMsg: Wrong password or login
#
# Method: private-key
# ErrorMsg: Public key not recognized
# ErrorMsg: Wrong signature
#
# Method: kerberos
# ErrorMsg: Kerberos GSS token is not verified
# ErrorMsg: Kerberos GSS user is not valid
# ErrorMsg: Kerberos GSS MIC is not verified
#

method=[^’]*
errorMsg=[^’]*

failregex = ^.*ERROR! Authentication with ‘.*%(method)s.*’ from host ‘<HOST>’ failed\. Error is ‘%(errorMsg)s’\.$

ignoreregex =

datepattern = %%Y-%%m-%%d %%H:%%M:%%S

———–
sudo cat /usr/NX/share/fail2ban/nxd.conf
———–
#
# Fail2Ban filter for NoMachine.
#

[Definition]

#
# Regex matches all accepted NX protocol connections.
#

failregex = ^Info: Connection from <HOST> port \d+ accepted on.*$

ignoreregex =

datepattern = %%a %%b %%d %%H:%%M:%%S %%Y

[Britgirl]

Hi,

what version of Ubuntu is it?

When you try to connect to the Ubuntu machine, what OS are you connecting from?

Are you able to connect from the Ubuntu machine to any of the other computers on LAN?

Do you get the same error if you start a session manually by clicking ‘Add’ and inserting the IP address in the host field, or by inserting the IP address in the ”Search” field, and clicking ‘Connect’?

If you right click the Ubuntu machine icon in Machines (it’s the icon with a pipe symbol), and select ‘Edit connection’, what do you see (attach screenshot please)?

related to https://forum.nomachine.com/topic/connection-time-out-trying-to-access-nomachine-ubuntu-desktop where you can find a workaround.

[Britgirl]

Nuertey, your file shows

Oct 12 16:42:15 ip-10-102-91-113.xxxxxx.com gnome-session[3258]: gnome-session-binary[3258]: WARNING: software acceleration check failed: Child process exited with code 1

You can try adding --disable-acceleration-check option in the gnome-session command in the DefaultDesktopCommand key, in /usr/NX/etc/node.cfg.

[Author]

Posts