Britgirl

[Britgirl]

How to disconnect a user from the host machine when the option to blank physical screen is enabled?

Remember that screen-blanking is a privacy feature. It’s there to stop users in the vicinity of the computer seeing sensitive information that the remote user (presumably the session owner) doesn’t want to show.  Currently, there isn’t a local key combination to permit a local user to unblank the screen to be able to disconnect the user connected from remote.

[Britgirl]

Can you tell us what the error is that appears when you try to connect to the Windows NoMachine server? Have I understood right that when you connect from the mobile app you can connect to this Windows server?

[Britgirl]

Hi,

The update is coming. If the final testing phase goes well, the update will be released in the next few weeks. Thanks for your patience so far.

Britgirl

 

[Britgirl]

The update is coming. If the final testing phase goes well, the update will be released in the next few weeks. Thanks for your patience so far.

Britgirl

 

[Britgirl]

The update is coming. If the final testing phase goes well, the update will be released in the next few weeks. Thanks for your patience so far.

Britgirl

 

[Britgirl]

Hi, NoMachine supports the following Linux distributions: RedHat, Centos, Fedora, OpenSuse/Suse, Debian/Ubuntu, and although ALMA is based on Red Hat, we don’t officially support it. However, that doesn’t mean that it should not work, so we tested the latest version on the fly. We reproduced the same problem. A possible workaround is to use Wayland as your display server instead of X.org. With Wayland we were able to start a physical desktop session with NoMachine.

[Britgirl]

Hi, can you check the permissions in Accessibility? In version we fixed a problem that meant that the user had to add NoMachine or nxnode (it depends on the version of NoMachine you have installed) to the list of allowed programs in System Preferences. Users will be required, after updating to v8, to add nxnode to the list one last time. Please see the TR for details.

https://kb.nomachine.com/TR10S10377

Does that fix it?

[Britgirl]

Sounds strange indeed. Could it be possible that the key release gets grabbed by another application and for this reason it’s not reaching the remote desktop? Since it only happens with the Right Ctrl, can you check whether there is a software or configuration using that key?

In any case, it would be useful to know which version of Windows, which Linux distro, what desktop environment on that Linux distro. I also assume you have the latest 8.2 on both client and server machines.

[Britgirl]

Are you in charge of the server or is someone else? Is it possible that some setting has changed since you last connected? I assume you are using the latest version 8 packages on both Windows and Linux sides. The error looks like that the server has been configured to not allow users who are not NX users.

Can you check how the following keys are set in server.cfg? Is it set to 0 or 1? 0 is the default setting when you install.

#
# Enable or disable NX users DB:
#
# 1: Enabled. Only users listed in NX users DB can login to the NX
#    server.
#
# 0: Disabled. All the authenticated users can login.
#
# If the NX user DB is disabled, any user providing a valid password
# from local DB or through SSHD authentication, can connect to the NX
# system. This is likely to be the default when SSHD authentication
# with PAM is enabled.
#
#EnableUserDB 0

[Britgirl]

Hi,

We’ve tested on Fedora 37 and not encountered authentication issues. Regarding failed authentication to change server settings, please start a terminal as the user attempting to authenticate and type:

sudo -l -U <username> /bin/pwd

What’s the output of above command?

 

the installation failed to find my external IP address, which has never been a problem with NoMachine before.

In NoMachine version 8, UPnP/NAT-PMP is disabled by default in the Free Edition. To get access to your computer over the internet, NoMachine’s UPnP/NAT-PMP port mapping must be enabled by hand (‘Server settings -> Ports’ -> Select the service and click on Configure); or alternatively, your router can be configured with the appropriate port-forwarding rule. When port-mapping/port-forwarding is enabled, remote NoMachine connections will be possible (more info section 2.2 https://kb.nomachine.com/AR04S01122).

Regarding the other issue you mention, it looks to be related to authentication

[Britgirl]

I’ve no idea what version you are using so I’m assuming you’re using the latest.

From your original topic what I understood was the non-sudo users couldn’t get access. What appears to be the problem is that you don’t actually have access with authorization. By default NoMachine does not let system users connect without acceptance of the desktop owner. So you must change the following setting:

You have two options. Either you add your username as a trusted user or change this key:

#
# Enable, disable or restrict NX Server requesting authorization to
# the owner of the physical desktop to allow a different user to
# connect.
#
# administrator: system and NoMachine administrators.
#
# trusted:       NoMachine trusted users for connections to physical desktop.
#
#
# system:        all unprivileged users who have a valid account to  login.
#
#
# owner:         the owner of the remote desktop.
#
#PhysicalDesktopAccessNoAcceptance administrator,trusted,owner

to look like this:
PhysicalDesktopAccessNoAcceptance administrator,trusted,owner,system

p.s I’d avoid having nx-derivatives installed on the same server with NoMachine.

Supporting earlier versions of NoMachine and NX
https://www.nomachine.com/AR07O00933

[Britgirl]

Check that you have not disabled “system” in the the PhysicalDesktopAccess key in the NoMachine server.cfg on your Debian server.

# Allow the given type of users to connect to the physical desktop.
# Set this key to 'all' to allow all kind of users, or to 'none' to
# completely forbid access to the physical desktop. Otherwise give
# a comma-separated list of values to indicate which type of users
# is allowed to connect, order is not relevant. Accepted values are:

#
# administrator: system and NoMachine administrators.
#
# trusted:       NoMachine trusted users for connections to physical
#                desktop.
#
# system:        all unprivileged users who have a valid account to
#                login.
#
# owner:         the owner of the physical desktop.
#
# guest:         Guest Desktop Sharing users who login anonymously
#                without having a system account and system guests
#                with an account generated on demand on the Linux
#                host. Guests are never allowed to connect to the
#                desktop of a cloud server.
#
#PhysicalDesktopAccess administrator,trusted,system,guest,owner

It’s enabled by default when you install NoMachine, but I’m not sure what changes you might have made (or made by others).

Check that the key includes system users e.g. PhysicalDesktopAccess administrator,trusted,system,guest,owner.

[Britgirl]

Sorry for not specifying. The changes in configuration must be made on the server side. Where I mentioned,

How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122

with reference to #2.2,  the person who needs to allow connections in will need to configure their computer as per those instructions that I mentioned in my earlier reply. They must then communicate the IP address to you and you use that to connect to their machine.

[Britgirl]

I have an Inovato Quadra. It runs an Armbian OS which is pre-installed with the XFCE desktop:

To be honest we’ve not tried NoMachine on  a Quadra. It’s one of many of these small devices on the market that to test all of them becomes impossible 😉 The same also applies to Armbian OS and Hampi. Systems and distributions we have tried and tested are listed in the dedicated article here, they are the most popular ones:

Installation & configuration notes for NoMachine Linux ARM packages
https://kb.nomachine.com/AR03M00842

You say changing the DefaultDesktopCommand key suggestion didn’t work. You didn’t say what the result was, but nevermind.

You could try the command:

grep ^Exec /usr/share/xsessions/*

You will see a list of commands which start all DE which you have installed on the system
You could choose one and set it in DefaultDesktopCommand key and see if with an alternative DE it works. More examples are here: https://kb.nomachine.com/AR04K00667

However, to cut to the chase (your original OP), and now that we have more info about what is installed on the Quadra

2. The Hampi system works as expected with the dongle (permissions are full, as expected, so system management can be performed) but, without the dongle, I have the permissions problem that I reported in my OP.

 

only logs would help us to identify what is happening. Enable debug, reproduce the problem with Hampi and zip up the logs. We can take a look. To do that follow the instructions here :

https://kb.nomachine.com/DT07S00243#2

Send to forum[at]nomachine[dot]com making sure you use the title of this topic as the subject of your email.

[Britgirl]

Thanks for the additional information.

And we got the logs for https://forums.nomachine.com/topic/user-unable-to-connect-to-nomachine-after-reboot as well 🙂

[Author]

Posts