fisherman

[fisherman]

if you are using Wayland, can you try to disable it?

[fisherman]

Hi,

Can you tell me if you have problem with lock screen when using physical or virtual desktop?

[fisherman]

Please just add your scripts in the node.cfg file, and it will be executed with current logged user.

[fisherman]

Please check following link for the additional information about possibility and how to run scripts:
https://knowledgebase.nomachine.com/DT11R00174#11.5

[fisherman]

Hello,

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 time

[fisherman]

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 1

[fisherman]

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 --nodeupdate after 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.

[fisherman]

Please apply requested change in the node.cfg file on the required Terminal Server Node that you want to allow only Xfce4 session.

[fisherman]

Hello,

Please set in the server.cfg and node.cfg
AvailableSessionTypes unix-xsession-default

and in node.cfg edit DefaultDesktopCommand.
DefaultDesktopCommand /usr/bin/startxfce4

[fisherman]

Hello,

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.

[fisherman]

Hello,

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 keys

[fisherman]

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/xfce4 or rm -rf /home/user/.config.xfce4
– log to the desktop with user physically or using NoMachine physical session
– then logout
– Create virtual desktop session

[fisherman]

If it is headless machine I would disable lightdm to start on boot, you can do that by executing
systemctl disable lightdm.service and then reboot machine.

[fisherman]

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.coreaudiod

[fisherman]

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.

[Author]

Posts