Forum Replies Created
-
Posts
-
FYI I have removed the image which shows “Desktop not shared” because it contains sensitive information.
Please tell us Linux distribution and version, desktop environment (LXDE, Gnome, KDE, something else?), and attach the exact message you see when you try to connect.
Hello, thanks for pointing out the articles, we’ll be checking them to make sure they are updated. About TLS, version 1.2 still is a reliable and widely used standard in the corporate world, Of course, whilst it’s obviously favourable to use the latest version, the move to TLS 1.3 is something we are already working on, as low priority.
This sounds like a permissions problem. Go to accessibility and screen recording permissions, remove nomachine/nxnode, then restart the NoMachine server (server settings > status > restart the server). Then go back to macOS System Preferences accessibility and screen recording and add permissions for the NoMachine application again. Check this illustrated guide on how to do this https://kb.nomachine.com/AR11Q01061)
Hi, the development roadmap is no longer in the public domain. Indeed they log the evolution and design of our software and are documents that go into extreme detail. There is a public section for Trouble Reports where we publish bug reports, the workarounds available and eventual closure.
Please send us debug logs from the computer you are connecting to. You should enable debug and then reproduce the problem. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Can you send us the logs from:
– your NoMachine Windows client
– the Ubuntu serverFor logs, please enable debug as per the instructions here on the Ubuntu side and gather logs. The link also contains instructions for extracting logs from the Player.
https://kb.nomachine.com/DT07S00243
Also useful would be the nxtrace from the Windows computer. If it’s the player which is crashing for some reason, there will be a nxtrace log in C:/ProgramData/NoMachine/var/log.
Send everything to forum[at]nomachine[dot]com. Please reference this topic in your email. Thanks!
Hi,
I would like to not enter the local “physical desktop”, but rather start a new session with another window manager (LXDE) when I work remotely…..ssh access does not work with the NM client, although is seems to be activated in the NM server config. SSH login is possible from a terminal using my standard rsa key (I would like to do this with NM as well instead of typing my password for each new session).
These are features of the NoMachine Terminal Server family of products. I suggest you take a look at the Workstation and check whether that satisfies your requirements. You can download it as evaluation software from the website here:
https://www.nomachine.com/product&p=NoMachine%20Workstation
https://downloads.nomachine.com/download-enterprise/#NoMachine-WorkstationMore information about how the two products are different is available here:
Differences between NoMachine Free Edition for Linux and NoMachine Workstation for Linux
https://kb.nomachine.com/AR10K00702So not KDE, which is what we thought you might have been using.
The first time you uploaded the logs, they failed to attach. If you have a chance to reproduce the problem again on Wayland, please follow the instructions here and send them to forum[at]nomachine[dot]com.
Please update the server side to the latest version 8. If you are not the administrator of that host, please ask them to reach out to us via the support center.
Can you send us the logs from the Windows 11 machine? Zip up the entire .nx folder and submit to forum[at]nomachine[dot]com. Include the link to your topic. Thanks!
This is a known issue and you should disable Wayland and use X.Org instead. See the following topics:
The Trouble Report currently open is: https://kb.nomachine.com/TR05V11141
We don’t know either. We tested MX Linux (having applied all the updates) and left the session running for most of the day and no slowing down was observed. If it comes back, next time, grab the logs.
Hi, can you try disabling hardware decoding on your Windows client computer? Follow the instructions here to do that (in your case you must disable completely, in point 3, by setting the option key as:
<option key="Enable hardware accelerated decoding" value="disabled" />How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202The distro and the DE would be useful for us to help us with our investigation. To find the desktop environments installed on your system 🙂
1) Execute this command in a terminal:
ls /usr/share/xsessions