Forum Replies Created
May 10, 2022 at 15:59 in reply to: Run script after connection and after disconnection #38590
Please just add your scripts in the node.cfg file, and it will be executed with current logged user.April 29, 2022 at 21:24 in reply to: Run script after connection and after disconnection #38470
Please check following link for the additional information about possibility and how to run scripts:
https://knowledgebase.nomachine.com/DT11R00174#11.5April 7, 2022 at 17:38 in reply to: Have shutdown NoMachine and can’t login #38236
Probably when you did select/ click NoMachine shutdown, you selected “Do not run NoMachine service at the next startup”, and now NoMachine is set to not start automatically after reboot.
after connecting to the machine use command to startup nomachine and to enable automatic startup.
sudo /etc/NX/nxserver --startmode automatic sudo /etc/NX/nxserver --startup
More information about start mode you can find here AR04L00800 – Disabling the automatic start-up of NoMachine at boot timeApril 1, 2022 at 17:43 in reply to: Forcing the server to 1024×768 #38147
If you are connecting to a host where NoMachine is set to create display, please use currently possible workaround to restrict resize of the display, by setting following key in the server.cfg
VirtualDesktopMode 1March 4, 2022 at 10:47 in reply to: How to disable Gnome xsession #37786
I have just tested and following this, we will limit NoMachine to use ONLY xfce4 on the requested node
On the node “node002.mynet.local”, please update keys in the node.cfg with:
AvailableSessionTypes unix-xsession-default DefaultDesktopCommand /usr/bin/startxfce4
then on the Enterprise terminal server execute
nxserver --nodeupdate node002.mynet.local:4000
in the nodeupdate command you will see output with
NX> 187 Session types available on node: unix-xsession-default
unix-xsession-default listed there means that on that specific node, only DefaultDesktopCommand /usr/bin/startxfce4 session will be started.
If this still does not work, send us your output of the command
--nodelist, output of the command
--nodeupdateafter editing node.cfg file, and node.cfg file from the requested node.
Please note this that if you have automatic node selection, sessions will be started possibly on the node where gnome is enabled.
In case you want to disable automatic node selection, please check following document: DT11R00178 – NoMachine Enterprise Terminal Server – Installation and Configuration Guide.March 3, 2022 at 15:17 in reply to: How to disable Gnome xsession #37774
Please apply requested change in the node.cfg file on the required Terminal Server Node that you want to allow only Xfce4 session.March 3, 2022 at 09:54 in reply to: How to disable Gnome xsession #37770
Please set in the server.cfg and node.cfg
and in node.cfg edit DefaultDesktopCommand.
DefaultDesktopCommand /usr/bin/startxfce4February 22, 2022 at 15:51 in reply to: Can’t close Little Snitch pop up on host #37668
What I see this is security feature of Little Snitch.
If you do need remote access Little Snitch, you have to enable the “Allow GUI Scripting access to Little Snitch” option in Little Snitch Configuration > Preferences > Security.February 18, 2022 at 09:45 in reply to: Mac client cannot use copy and paste text to NoMachine Linux #37617
NoMachine remote connection behaves as the local keyboard was directly attached to the server. Due to that, since you need to press Ctrl+C to copy on Linux, you have to press Control+C also when connecting remotely from the mac.
There is an open feature request that will cover that problem when it is implemented FR10M02977 – Provide an interface enabling user to configure modifier keysJanuary 24, 2022 at 14:08 in reply to: Trouble connecting to Linux Mint XFCE desktop #37150
I did not check startup scripts for the Linux Mint that loads correct theme on physical desktop. NoMachine starts command you mentioned in your post. I can recommend workaround that possibly you can use.
– Remove existing xfce settings for that user that has loaded standard xfce desktop.
rm -rf ~/.config/xfce4or
rm -rf /home/user/.config.xfce4
– log to the desktop with user physically or using NoMachine physical session
– then logout
– Create virtual desktop sessionJanuary 18, 2022 at 17:10 in reply to: Cannot connect to remote Linux server running NoMachine #37083
If it is headless machine I would disable lightdm to start on boot, you can do that by executing
systemctl disable lightdm.serviceand then reboot machine.January 12, 2022 at 15:17 in reply to: MacOS Monterey v12.1 server – no audio sound on both Windows/Linux clients? #37018
What I noticed is that you can use possible workaround to solve audio problem on Mac OS 12
sudo rm -rf /Library/Extensions/nxaudio.kext /Library/Audio/Plug-Ins/HAL/NMAudio.driver /Library/Audio/Plug-Ins/HAL/NMAudioMic.driver sudo mkdir -p /Library/Audio/Plug-Ins/HAL/ sudo cp -a /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/NMAudio.driver /Library/Audio/Plug-Ins/HAL/NMAudio.driver sudo cp -a /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/NMAudioMic.driver /Library/Audio/Plug-Ins/HAL/NMAudioMic.driver sudo chmod -R 755 /Library/Audio/Plug-Ins/HAL/NMAudio* sudo chown -R "root:wheel" /Library/Audio/Plug-Ins/HAL/NMAudio* sudo launchctl stop com.apple.audio.coreaudiod sudo launchctl start com.apple.audio.coreaudiodJanuary 10, 2022 at 16:44 in reply to: MacOS Monterey v12.1 server – no audio sound on both Windows/Linux clients? #36993
About MacOS 12 we have already opened Trouble Report that will be fixed in the following NoMachine versions TR12S10423 – Sound forwarding doesn’t work on macOS 12.January 10, 2022 at 14:13 in reply to: Android client: right mouse click #36981
I am glad that it helped.January 10, 2022 at 14:04 in reply to: No hardware decoding / Mint 20.2 / GTX970 #36979
Furthermore, problem is with nvidia drivers and not with NoMachine software.