Forum Replies Created
It’s not quite clear what your question is but when connecting with NM you are connecting to the physical display.
You can close the session in two ways:
- Click X of the NoMachine window and you will close the session but still be logged in locally, and you can enable session lock on disconnect. You can find more information here FR05N03110 – Locking the screen automatically when the NoMachine session is disconnected – Locking the screen automatically when the NoMachine session is disconnected
- Log out from Windows and then close the session, in that case you will need to log back in.
If you are using Enterprise Desktop, you can force the system log out if this is your preference, see here for details FR08R04011 – Forcing a system logout when the user disconnects from the physical display
It looks for me from the nxserver –restart command that NoMachine does not detect physical desktop on that host. Can you tell me your OS and Desktop environment you have on that host?
Based on the command output it looks some of NoMachine service are not running. you can confirm it by running command
sudo /etc/NX/nxserver --status
To be able to debug specific problem we would need to collect debug logs. You can enable them by:
sudo /etc/NX/nxserver --debug --enable all sudo /etc/NX/nxserver --restart
Reproduce the problem.
sudo /etc/NX/nxserver --debug --collect sudo /etc/NX/nxserver --debug --disable all
Please attach logs to your reply here or you can send them to forum[at]nomachine[dot]com making sure to use the topic’s title in the subject.
about authentication please can you check this article AR03S01118 – Username formats supported to log-in to NoMachine by password authentication.March 29, 2021 at 11:52 in reply to: How to maintain aspect ratio in fit to window mode? #32651
I tried and feature worked correctly for me. Can you tell me what is the OS and NoMachine version you are using on client and server side.
Additionally please can you make sure that when you are using the mentioned feature that “Scale to window” is enabled in player as shown on the screenshot.
What I can say that currently serveradd needs to pass mentioned steps in order to add server to the CS. You can easy eliminate one by using –strict-host-key-checking no in the –server add command
/etc/NX/nxserver --serveradd newserver.domain.com --strict-host-key-checking no
There is an easy possibility that for the to automate multiple serverad using expect script.March 25, 2021 at 08:56 in reply to: NoMachine and best settings for high latency network #32586
Please check this article https://www.nomachine.com/AR04M00845.
Latency as mentioned in the article can impact responsiveness of the session. I would recommend that you try NoMachine software.March 24, 2021 at 09:38 in reply to: Black screen on Ubuntu (virtual machine on Oracle cloud) #32551
We do not reproduce similar issue.
Please collect NoMachine logs following document https://www.nomachine.com/DT11R00182.
Additionally get node.cfg file located in /usr/NX/etc and output of the following command
Can you please send them directly to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email?
If you want to disable file transfer, you can do this by editing the cfg files as explained in that article I mentioned in my earlier reply. I don’t know what permissions your users have. If they don’t have administrator rights on the server, then they won’t be able to re-enable it.
Or you can do it in the server UI itself. Again, this depends on what permissions your users have on the server host. If the connecting user is an admin user, it’s impossible to prevent them from accessing the server preferences.
Regarding the ports, you must have port 4000 open in order to accept connections in general. If you disable it, you won’t be able to connect at all. Ports 22 are for SSH connection on Mac/Linux and 4022 on Windows.
You can check this document https://www.nomachine.com/DT11R00185 Enabling and disabling the NoMachine device sharing services manually.
All needed configuration requested will require administrator rights.
about used ports in NoMachine you can check following Link https://www.nomachine.com/AR01L00770 Default ports used by NoMachine 4 or laterMarch 10, 2021 at 19:01 in reply to: Magic packet not waking up after set to sleep by NoMachine #32337
I tried to reproduce your problem without success. Additionally I dont see relation with NoMachine, especially as Wake on LAN is the client side feature.
Can you verify router configuration and if your remote magic packet is correctly sent to the MAC address of the server.
1. Can you make sure that devices under /dev/dri are also in video group and have correct permissions
ls -la /dev/dri
2. we have hard coded path to look for iHD driver in /opt/intel/mediasdk/lib64/
You could try to create these directories and add symbolic there. so something like:
mkdir /opt/intel/mediasdk/lib64/ ln -s /path/where/he/has/iHD_drv_video.so /opt/intel/mediasdk/lib64/iHD_drv_video.so
Thanks for the info. I am glad that you solved the problem.
If you are using headless server, please check following article https://www.nomachine.com/AR03P00973.
can you link following libraries in folder /usr/lib/x86_64-linux-gnu/
ln -s libva.so.2 libva.so ln -s libva-drm.so.2 libva-drm.so