Forum Replies Created
-
Posts
-
Are you being shown the question: “Cannot connect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?” right? Can you choose “No” and wait to see if the session appears on the session list?
NX server logs from server side would be helpful to investigate problem. Please enable debug, reproduce problem and send logs to forum[at]nomachine[dot]com. There is instruction how to enable and collect debug logs automatically: https://www.nomachine.com/DT10O00162
In the meantime is there a way to restart the NX server on a machine either remotely or via the command line that I could use next time this happens?
Command for restart nxserver is
sudo /usr/NX/bin/nxserver --restart, you can also execute it remotely using SSH.Can you check if the problem still appears if you disable Xserver and allow NoMachine to create its own virtual frame buffer?
To do that – stop the running Desktop Manager (open terminal or connect there via SSH and execute command:
sudo service lightdm) and restart nxserver (sudo /usr/NX/bin/nxserver --restart). Now you should be able to connect there via NoMachine and create a session.Please refer to these articles:
https://www.nomachine.com/AR02P00963 (How to start the session by passing options to the client from command line)
https://www.nomachine.com/DT10O00159 (The most frequently asked options for pre-configuring the client and the session behavior)
This doesn’t look like it’s a problem related to NoMachine.
However you can try to check if firewall rules are still on the system (run PowerShell as an administrator
netsh advfirewall firewall show rule name=all | findstr "NoMachine") and delete them (netsh advfirewall firewall del rule name="ENTER_HERE_RULE_NAME").What’s your Windows version by the way?
The only thing in the NoMachine installation which can be related with network is nxtun driver. And it’s extremely rare that uninstalling would not remove said driver. However, to make sure, check whether it still appears (open CMD as an administrator and execute command:
driverquery /V | findstr nxtun).If for some reason it is still there – remove it. To do that open Control Panel -> “Device Manager” -> “Network adapters”. Click right mouse button on the NoMachine VPN Adapter and choose “Uninstall device”.
NX protocol doesn’t support option to use ssh-agent. SSH protocol does, but connection via SSH to the server where is NoMachine free version installed via SSH is not available.
…so that I don’t have to type my private key pass-phrase every time I connect
You can use option “Save this passphrase in the file connection” or generate key without passphrase to achieve it.
SSH connections are available only on Enterprise products aimed like Workstation, Terminal Server and so on. The free product, NoMachine, does not support connections by SSH. However it’s possible to set up key based authentication with NX protocol. Please refer: https://www.nomachine.com/AR02L00785.
It looks like you’re using Gnome 3D, but you prefer Gnome Classic. Just edit the /usr/NX/etc/node.cfg file, find and change line with DefaultDesktopCommand key to:
DefaultDesktopCommand "env GNOME_SHELL_SESSION_MODE=classic gnome-session --session gnome-classic"as it’s in the article: https://www.nomachine.com/AR10N00906.
You should follow the instructions to disable the automatic start-up at boot time using this article: https://www.nomachine.com/AR11P01005. Note that users need to have administrative privileges to change this settings. Let us know if that doesn’t help.
I saw the checkboxes for blanking the physical console (but it didn’t work)
Is that a virtual machine? You need to know that blanking features applies only for physical monitors.
The NoMachine virtual desktop functionality is available on remote Linux host with Workstation, Small Business Server, Terminal Server, or Enterprise Terminal Server.
However, NoMachine is able to use its own display service (that is an embedded X server) to let users connect seamlessly a physical desktop running in background on the remote machine when that Linux host doesn’t have an X server running (e.g. a headless machine).
To disable Xserver you can for example use
sudo init 3command. After disabling Xserver – nxserver restart is needed (sudo /usr/NX/bin/nxserver --restart).We are not able to reproduce this problem.
What version of NoMachine is installed on your Windows computer? Is UPnP enabled? You can check it with command:
grep EnableUPnP /usr/NX/etc/server.cfg.More information on how to connect when the server is behind a firewall or NAT router you can find at the following link: https://www.nomachine.com/AR11L00827.
Are you sure that you added port 4000 to the access rules? It’s “Configuring the security group” section in mentioned article.
To disable X server permanently you can execute command
sudo systemctl disable gdm3.service(if you have gdm3 of course).That TR is an issue affecting NX 3.5.0. NX 3.5.0 is a legacy version, no longer supported. The forums are dedicated to the most recent version.
Which NoMachine version is installed on both sides? Can you check nxserver status on the server side – is it running? Is it also Windows on the server side? Did you reboot after installing NoMachine?
We didn’t have problems with enabling UPnP and changing port in our labs. Did you try connecting before changing port and it worked?
Can you show output of the
sudo /usr/NX/bin/nxserver --upnpstatus?
Did you restart nxserver (sudo /usr/NX/bin/nxserver --restart) and initiate port mapping (sudo /usr/NX/bin/nxserver --upnpmap) after you have changed port?