Britgirl

[Britgirl]

Thanks for following up with that. Are you using NoMachine 8.13 both sides? Can we know the desktop environment on the Raspberry? Is it KDE or something else?

[Britgirl]

Thanks for reaching out. The implementation of the feature”Integrating the NoMachine window fullscreen mode with macOS Spaces management”  was postponed to a later release. We fully understand that it this is important for our Mac users. We’ve not dedicated the necessary resources simply because of other development priorities related to version 9 and NoMachine Network. Once v9 is out, we can start on integration.

We moved our development roadmap from the public knowledge base, as you probably read from the message that appears when you click on a link to any FR.

[Britgirl]

Did you restart the NoMachine server as printed in the message? Go to settings > server > restart the server. Then connect again.

[Britgirl]

I don’t know what those instructions are about but you should be looking in the official documentation from MS. There are also multiple tech websites providing the steps on how to configure the policy.

Connecting without a password is not something we recommend, as the article I pasted earlier mentions. Using NoMachine’s own User DB is a possible option. You can create a user and password only for NoMachine usage. It avoids interfering with Windows registry keys and avoids changing your local user account configuration.

– Open notepad or other text editor as administrator
– Open server.cfg, which is in %ProgramFiles%/NoMachine/etc
– Find, uncomment (ie. delete the # sign from the beginning of the line) the following keys and save:
EnableUserDB 1
EnablePasswordDB 1
– Open CMD or powershell as administrator and execute: cd C:\ProgramData\NoMachine\nxserver
– Execute nxserver.exe --useradd USER where USER is your account without password. Then you will be asked to create password. That password will work only for nx connections. It doesn’t change your local account configuration.

Then, go to the device you want to connect from and insert the user credentials with the password you created on the Windows server.

[Britgirl]

Open the On-Screen Keyboard on the Windows host, and press the NumLock key there (you will need to turn on the numeric key pad in the On-Screen Keyboard, that is reachable from the Options button). Is that enough to use the numeric pad from the Mac?

[Britgirl]

In version 8 it is configured on the server side using the EnableCredentialsStoring key in the server.cfg. Also present in the free version. Find the key and set it to

EnableCredentialsStoring none

You can find more info about this key and the configuration files is available, for example, here: https://kb.nomachine.com/DT07S00246#3.3

 

[Britgirl]

Hi,

NoMachine currently supports Yubico authentication by configuring PAM. You can read more about how to do that here:

How to enable Yubico authentication with NoMachine on Linux
https://kb.nomachine.com/AR12Q01064

[Britgirl]

Can you show us the output of the ‘setxkbmap -print’ command run inside the xrdp session?

[Britgirl]

Hi, are you connecting to the NoMachine Windows server from the Mac? The title suggests the Mac has no numerical keyboard, but what you wrote in the body indicates that it’s the Windows computer without the numerical keyboard. Can you confirm? 🙂

[Britgirl]

Here, what’s important to consider is not necessarily how NoMachine performs when capturing and encoding the display, but rather the performance of the Gnome desktop with and without GPU encoding. You might find that Gnome performs substantially better with GPU. There are many variables to take into consideration and you need to test it on your own system in your own environment. You might find that a “lighter” desktop such as XFCE or Mate fits your use case better.

[Britgirl]

Hi, please take a look at the following article:

How to connect to Windows with NoMachine and an empty password
https://kb.nomachine.com/AR05L00802

You have two options. Configure your account to use a password, which is strongly recommended, or configure your Windows OS to open the appropriate policy to allow remote access without a password.

[Britgirl]

Please disable HW encoding on the server side. Go to Server settings > Performance > make sure the box “Use hardware encoding” is not ticked. Does that help?

[Britgirl]

There are logs missing from the server side from user’s homedir/.nx. Additionally, you are using 8.11. It would be useful to update to 8.12 and get fresh logs with debug enabled. Make sure you zip up the entire .nx from the NoMachine Windows host you’re connecting to. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243.

Edit 10/10/24 – no new logs were received. We suggest to update to the latest 8.14 and if you continue to have issues, open a new topic with the full logs attached.

[Britgirl]

Are you using the default packages of MX Linux or did you apply all the updates?

Logs would be useful. Everything was fine and suddenly it wasn’t suggests that maybe some update broke something, maybe some drivers. To get NoMachine logs from the MX Linux installation,  enable debug, reproduce the slowness and then zip up the logs. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

This seems to be related to your Linux host being headless, ie. without a monitor. You probably don’t have a monitor plugged in so, you should stop sddm and restart nxserver.

sudo services sddm stop

sudo /etc/NX/nxserver --restart

Then NoMachine will create its own virtual display. To avoid sddm restarting itself after a future reboot, disable it completely

sudo systemctl disable sddm

Information about headless hosts is available here: https://kb.nomachine.com/AR03P00973

[Author]

Posts