Forum Replies Created
-
Posts
-
In your script possibly instead of:
service nxserver startUse this:
service nxserver start > /dev/null 2>&1 &or
/etc/NX/nxserver --startupHi.
UserHome applies only to newly created users. For existing users, /usr/NX/etc/node.cfg key with correct path must be set:
UserNXDirectoryPath “”
Are you using home sharing with samba? If yes, can you verify isn’t it similar problem https://www.raspberrypi.org/forums/viewtopic.php?t=158919? It doesn’t sound it could be related to NoMachine. Please verify if it’s possible to connect to that machine over terminal – via ssh and if home directory of the affected user have correct ownership or if it’s shared at all.
Is there Wayland on that Ubuntu? If yes – check solution mentioned by @Tor: https://forums.nomachine.com/topic/macos-remote-special-keys-never-get-forwarded-even-with-grab-keyboard-mouse#post-33454
Hi.
Please refer to the article: https://knowledgebase.nomachine.com/AR10Q01058. If you want to start nxplayer with option –activegrab by default quit nxplayer, edit file $HOME/.nx/config/player.cfg and enable active grab key:
<option key="Enable active keyboard grabbing" value="true" />Clear NoMachine installation shouldn’t occupy more than 200 MB (the size depends on the type of package installed). You can check the size of the installation path (in the default is /usr/NX), including the nxserver log path (in the default it should be in /usr/NX/var/log, more about logs you can find there: https://knowledgebase.nomachine.com/DT11R00181).
Check also specified paths for program files and connection settings, transferred files and recordings, which you can find here: https://knowledgebase.nomachine.com/DT11R00177#2.4.
Hi
We didn’t notice such kind of issue. Please reboot the system and install the program properly. After that, you should be able to uninstall NoMachine. (https://knowledgebase.nomachine.com/DT10R00166#2.2).
Hi,
You can try the new line sequence “\n”, for example:
NodeLoginGreeting “Hello\nWelcome to your NoMachine session\nHow are you today?”
Also, it would be preferable for this message to be displayed *before* someone logs into a NoMachine session. Is that possible?
Check node.cfg key: UserScriptBeforeSessionReconnect. More info about user scripts you can find there: https://knowledgebase.nomachine.com/AR02L00787
Hi,
We tried the same OS and had no problems neither with the detection of the desktop nor with the start of the nxserver service with systemctl. Maybe as you said installation was broken during the update and your disk was out of space? Please try to uninstall the program (
sudo /usr/NX/scripts/setup/nxserver --uninstall && sudo rm -rf /usr/NX /etc/NX) and install again the newest version.Is the local connection still working? If it’s not a problem with the credentials maybe try to unselect “Use UDP communication for multimedia data” (it’s in the player – in connection file) in case UDP ports are blocked in the router.
Logs from both the client and server side would be helpful to investigate the problem. You can send them to forum[at]nomachine[dot]com, making sure you add the title of the topic as the email subject. Instructions about debugging and collecting logs can be found here: https://www.nomachine.com/DT11R00181.Hi,
If your router doesn’t support UPnP, External IP won’t show in the nxserver command output or nxplayer GUI. Please try port forwarding (which you already configured). Reverse all UPnP changes you made in server.cfg and make sure if the chosen port is not being used by another service. To connect you need to open a new connection in the nxplayer, enter your Public IP and use forwarded port (in your case 21960).
Hi,
We cannot reproduce such a problem on Ubuntu with Mate. Are you able to take a look if the problem isn’t shown also on that machine, on the physical monitor? Maybe it’s headless?
Could you please check if the problem happens when you disable the X server and restart nxserver (check also if
DefaultDesktopCommand mate-sessionis set in/usr/NX/etc/node.cfg)?
You can find more information about problems on headless machines here: How to solve black screen and other possible problems on headless machines.It looks that your BT hub is in NAT mode and the desktop PC is not in the network broadcast by this device. To be able to connect to machines in that mode you need defined manual forwarding rules. To avoid that set BT hub to Bridged mode. Then both devices will be in the same subnet.
Hi.
Do you have access to that machine (for example through ssh)? Is there plugged monitor? Please try to stop X server (
sudo init 3) and restart nxserver (sudo /etc/NX/nxserver --restart). More about problems with headless machines you can find there: https://www.nomachine.com/AR03P00973