Forum Replies Created
-
Posts
-
It looks that there is a problem with the pam_mount module when creating sessions. Please refer to this article: How to solve hanging problems when creating a NoMachine session (pam_mount module is in use)
Did you reinstall NoMachine? We are aware of a similar problem. Please take a look at this Trouble Report: Problem uninstalling a version 7 and then installing version 7.1.3.
If this is your case, please use the described workaround.We weren’t able to reproduce the problem. Can you please tell us more about the issue? What error does it show? Are there nx processes after reboot (
ps aux|grep nx)? Are connections possible after manual nxserver start (sudo /usr/NX/bin/nxserver --startup)?Hi.
Try set:
DefaultDesktopCommand "env XDG_SESSION_TYPE=x11 /usr/bin/dbus-launch /usr/bin/startxfce4"
in /usr/NX/etc/node.cfg.Do you have Desktop Environment (DE) installed on that debian? Is it headless? There is article with instructions how to install some GUI on linux: https://www.nomachine.com/AR04K00667#4.
If it’s headless after DE installation, please set adequate DefaultDesktopCommand in /usr/NX/etc/node.cfg (take a look on point 2.1 in mentioned article) and restart nxserver (
sudo /usr/NX/bin/nxserver --restart). Then you should be able to connect.Did you try to use other Desktop environment then default (Tips for using NoMachine on NVIDIA Jetson Nano)?
Hi.
Please uninstall NoMachine with following command:
sudo dpkg --purge nomachine && sudo rm -rf /usr/NX /etc/NX /var/NX .nxIt will remove program and all its configurations from the system. Then you will be able to install NoMachine properly.
Follow up @graywolf post https://forums.nomachine.com/topic/connection-fails-on-headless-client#post-21783 and in step 2 use those command:
DefaultDesktopCommand “env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus /usr/bin/startplasma-x11”
Hi.
If you used the previous workaround – and installed XFCE4 – physical desktop with XFCE4 works fine. We can’t test with that specific model of camera you are using unfortunately, but that error you posted is related to nvidia drivers, it seems:
https://forums.developer.nvidia.com/t/nvivafilter-could-not-get-egl-display-connection/69307
Hi.
We aren’t able to reproduce. It’s little looks like when you have monitor unplugged – desktop isn’t detected somehow and then you are creating a new desktop during connection. Because physical exists and you are created a new one with the same user – browser is opening on other display (or just cannot be open on this display). Is could be the case?
Please try Tip 2: Connecting to a headless Raspberry from article: https://www.nomachine.com/tips-on-how-to-set-up-your-raspberry-pi-for-remote-access-via-nomachine
Edit RPi config file
sudo vim /boot/config.txt, find, uncomment and set key:hdmi_force_hotplug=1. Save the file and reboot device.Did you use the instructions from the section “Using NoMachine for remote access to a computer over the internet” from: https://www.nomachine.com/getting-started-with-nomachine?
For more details please refer: https://www.nomachine.com/AR10R01099.
We cannot reproduce this problem. Is that Buster for armv7 (you can check your architecture with command
uname -a)? Please open terminal and execute:/usr/NX/bin/nxplayer --dialog statusand report what happened.If you trying connect over internet you need configure port forwarding or enable UPnP. Please refer to: https://www.nomachine.com/AR10R01099
To use a NX account, do I first need to create a system account with the same name?
Yes, there should exist local or network account with the same name.
Can I configure NoMachine to allow AD users to authenticate with their AD credentials, but then they view the currently logged-on user, which is a local account?
Yes, enabling Users db and adding AD users will allow only them to login to Your host. If You doesnt enable Nx Password db, then NX will login them using their AD credentials. To enable users db, set following key in the server.cfg:
EnableUserDB 1
All added user which aren’t desktop owner, trusted or administrator – would require the approval of the desktop owner. The desktop owner also can allow or forbid the user to interact with the desktop.