Forum Replies Created
-
Posts
-
I would prefer Wayland, if some future version of NoMachine will support it.
NoMachine already supports Wayland 🙂 It has done since version 6. But given there are some limitations with desktops on Wayland in general, this will affect the remote desktop experience as well.
Please see here:
Notes for connections to Linux physical desktops running Wayland
https://kb.nomachine.com/AR02P00969Can you send us the logs of the Ubuntu server? Please see the following document for instructions and submit them here or send to forum[at]nomachine[dot]com, making sure to use the topic’s title as the subject of your email. Thanks!
Happy to know you noticed the improvements. There is actually some big news on the WebRTC front. We are reworking the way it works, in the new versions of NoMachine, and we plan to make it the default soon, in upcoming versions. No ETA as yet though.
NoMachine Enterprise Desktop for Mac so that it is not required to add NoMachine to the Privacy->Screen Recording settings.
Any NoMachine product for Mac must be added to Apple’s permission via GUI and it can’t be done via CLI. In version 8 we fixed an issue affecting these permissions which were being reset every time you updated your macOS version. Now, in version 8, you add NoMachine to macOS permissions once, and will not need to do it again.
Hi, logging of file transfer activity is available in version 8
This feature allows system administrators to audit all activities about transferring files from client to server and vice-versa. The log contains information like the file name, the direction of the transfer, the size in bytes, start and end dates, the result and the transfer rate, information which can be easily parsed by custom scripts.
The key to enable is:
#
# Enable or disable the creation of file transfer logs for auditing
# purposes. Logs contain the word ‘Audit’ and are logged also to
# server log file.
#
# 1: Enabled. File transfer operations are logged into server log.
#
# 0: Disabled. File transfer operations are not logged in server log.
# This is the default value.
#
#EnableAuditlogs 0node.cfg
Session recording events is definitely something we can evaluate adding to extend and improve the current support for auditing.
In version 7 and onward, enabling log_level to ‘7’ will show all events useful for debugging. If you want to view details about user access, session ID etc, you can view this type of information by running ‘nxserver –history’. For example, you can read more about this here in the Enterprise Desktop guide: https://kb.nomachine.com/DT07S00246.
Hi, we got your last message about enabling logs. We’ll wait for you to submit them.
You also mentioned you had some issues with automatic updates i.e NoMachine didn’t auto-update or show info about latest update, and you had to manually check the update? And subsequently the update process would fail when downloading?
Logs about manual installation can be found in the /var/log which on Linux is usr/NX/var/log/ and on Mac it’s /Library/Applications Support/NoMachine/var/log. We’d need to see the nxinstall.log and nxupdate.log.
Logs about updating via the GUI are in $HOME/.nx directory. To collect those you need to enable “Don’t delete logs on exit” in “Player Preferences” -> “Privacy” and then reproduce the error. If you reproduce it, submit the the entire /Users/
/.nx directory. To properly collect those logs you can take a look on this article https://www.nomachine.com/DT04M00076#6.
What is the difference between the free version and the enterprise version?
You can compare the two products here 🙂
https://www.nomachine.com/remote-access-for-everybodyIf you scroll down on that page, you can also compare the support options which I think is what you are asking in your last follow up?
Hi,
like I wrote last time in the topic here:
https://forums.nomachine.com/topic/no-sound-for-snap-installed-applications-ubuntu-22-04-1-arm64#post-39926We’re not able to reproduce and need logs. Instructions in the link above.
The recent version didn’t change anything which could affect how NoMachine connects to remote Windows (headless and non).
Try these settings, by adding them one at a time to the node.cfg on the Windows computer you are connecting to.
First add
DisplayServerExtraOptions "-displayrequired"and start a session. If that doesn’t improve, add
DisplayServerExtraOptions "-nodxgrab -nodxgigrab"regardless of what I use to connect to it
So it’s something affecting every remote access tool you choose 🙂 not just NoMachine?
If that GPU doesn’t work normally when monitor is powered off, it’s possible that there is nothing we can do.Hi, we are aware of this and have opened a Trouble Report which you can monitor here:
https://kb.nomachine.com/TR10T10632The fix is planned for the next maintenance.
Hi 🙂
something similar was reported by another user here:
https://forums.nomachine.com/topic/issues-connecting-to-manjaro-kde-plasma
which is being caused by the nvidia drivers and not by NoMachine. Can you try disabling HW decoding on the Player machine?
Edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”.
Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’.
Then re-open the Player and connect again.Another thread on our forums also reports more about the cause:
Hi Dammé,
can you send the log files/attachments that didn’t upload to forum[at]nomachine[dot]com? Use the title of this topic as the subject of your email. Thanks 🙂
Hi, it looks similar to another topic https://forums.nomachine.com/topic/issues-connecting-to-manjaro-kde-plasma. In that case, disabling hardware decoding on the client side helped.
We would be interested in seeing the backtrace of the ACER box to make sure. Can you check for segfaults on the Player side? This article explains how to look for core files, https://kb.nomachine.com/AR09L00810.
After that, in the Player computer, please edit option key=”Enable hardware accelerated decoding” value=”disabled” in player.cfg. Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’. Then try to connect from your ACER client again.