Forum Replies Created
-
Posts
-
Please can you verify if nomachine client is installed correctly, you can do easy that by executing
dpkg --list "nomachine*".If NoMachine is installed, but failed to start, then please check your client host architecture
uname -m.
If your architecture is x86_64, please use NoMachine client package Nomachine client amd64.Hello,
NoMachine on Mac OS uses connection to the physical display. “Unknown Display” and only resolution choice of 1080p could be limitation of connected monitor or limitation of headless Mac.
If you are using headless mac, possibly attaching hdmi dummy adapter would help.
Or you could try to hold Option
⌥when selecting Scaled resolution (see screenshot).Attachments:
Based on the information I found on the Internet, I see that Wayfire is Wayland environment and cannot be used within NoMachine to start virtual desktop sessions. You could try and install one of the other DE like KDE, Gnome, XFCE4 on Garuda and use it within NoMachine.
You can open CMD as administrator, and execute following command:
"C:\Program Files (x86)\NoMachine\bin\nxserver.exe" --restartNoMachine old version 3.5 was creating session configuration differently. NoMachine from version 4, can use most of the parameters configured during the session, Please check Guide to the Functionality in the Menu Panel on Mac.
additionally please check this document to see how to change port of the connection Getting started with NoMachine.I would recommend that you remove NoMachine Enterprise Desktop with following
rpm -e nomachine-enterprise-desktop rm -rf /usr/NXthen do clean installation of NoMachine Cloud server.
I would just add that NoMachine Cloud server is done mainly to centralize access to # of different NoMachine servers. More information you can find What NoMachine server products can I use with Cloud Server
I would say that to achieve situation that on every command you create new session you will need to disable autoconnect in ConnectPolicy key in server.cfg
ConnectPolicy autocreate=1,autoconnect=0,automigrate=0,desktop=0,dialog=0,xsessions=0,udp=1We would need additionally nx logs from the home folder.
you can easy create an archive and send it to use by executing following command:
sudo tar -cvzf macServerSideLogs.tar.gz /Library/Application\ Support/NoMachine/var/log $HOME/.nxor check our automatic log collection feature https://knowledgebase.nomachine.com/DT11R00182
You can get all needed logs by executing
/etc/NX/nxserver --debug --collectBased on the logs you posted, it looks NoMachine is not installed on the server host you are trying to connect.
Please can you ask administrator to check if NoMachine is installed on mentioned hosts.
graywolf asked correctly to re-enable nxnode permission in system/ Security & Privacy/Accessibility.
About permissions you can see more on following article: https://knowledgebase.nomachine.com/AR10P01001.
You can disable “Match the client resolution upon connecting” see attached iPad screenshots.
Attachments:
Can you check following article https://www.nomachine.com/accessing-your-remote-desktop-on-google-cloud-platform-via-nomachine.
I am not sure that I fully understood the problem. What I can advice that you check following NoMachine article Switching the view between multi-monitors during a remote desktop session.
If this does not help, can you maybe describe in details what is the OS on server and possibly screenshot of display arrangement of server and client.
upnp needs to be enabled on your home router, or you will need to do manual port forwarding. You will need to consult your router manual how to do it.
NoMachine on Windows does connect to the physical screen thus requires entering login information on Windows login screen. I noticed that there is dismissed out of scope FR that was suppose to solve that problem https://knowledgebase.nomachine.com/FR05N03109.
