Forum Replies Created
-
Posts
-
I just realised there is a ‘1’ missing in the key I wrote. I apologize for that.
The key should look like this:
DisplayServerExtraOptions “-displayrequired 1”Hi, thanks so much for your feedback 🙂
but in many other contexts, like the context we have, with machines both inside and outside the network.
This is exactly why we implemented it, to make adding nodes to your Cloud Server as seamless as possible.
you’ve changed the way you pick mouse position in Wayland, directly from udev which conflicts with other virtual input devices, blocking access to the remote desktop’s input, when the same is running an automation task…attempt to get mouse movements/control on the NoMachine client side.
What you describe is a new feature giving keyboard and input events from the local user logged-in to the remote computer priority over input generated by the user connected via NoMachine.
It is mainly intended to add a further security level to desktop sharing, so that the input (mouse and keyboard) of
the remote user connected by NoMachine will be effective only after the local user doesn’t produce any input for a certain period. When the NoMachine user gains control over keyboard and mouse, the local user can stop him/her at any moment by simply moving the mouse or typing something.To disable this behaviour, you can set this in node.cfg:
DisplayServerExtraOptions "-eventdelay 0"Your Android app is unparalleled when it comes to ease of access and keyboard functionality, and with Wayland support, you’ve been paramount to a whole section of the Linux comunity. We’re not going anywhere, we just want to use the old v7 server.
That’s good to know 🙂 You can try contacting the web team via the website to see if they can share a link to the earlier version. But first we would appreciate knowing if the -eventdelay setting improves things for you with regard to the mouse position issue you mentioned.
Regarding the SW/HW/white screen issues described in the thread, we are still investigating.
To create your connection to the remote computer, click on ‘Add’ which you can see in the image you attached, top left.
Then, if you are connecting on LAN, you need to know its private IP address which is assigned to your specific device. See Fig. 1 in https://www.nomachine.com/getting-started-with-nomachine. If you are connecting over the internet, you will need its external IP address.
There are two ways you can check your computer’s IP address in NoMachine. (i) When you’ve installed NoMachine on the computer you want to connect to, open NoMachine from the programs or applications menu. A Welcome panel will publish the local IP address of the computer on which you have installed the software. Or (ii) click on the !M icon (the NoMachine Monitor) which is visible in the computer’s system tray. Click on ‘Show the Server Status’.
I then need to set the password for this connection,
To be able to connect to a Mac or PC from remote you need to have a system user account for that computer (username and password). The password along with the username is what lets you authenticate to the desktop and connect to it. For attended desktop scenarios it’s possible to allow guests to connect, i.e they don’t need a username and password, but they will only be able to connect with your authorization.
The second connection on this image attached looks like a connection to a local PC, but I don’t see how to set that up
The second connection, which has a “little pipe” indicates all computers with NoMachine (server) installed (more about this here https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network). So if you want to see other NoMachine-enabled computers on your LAN, you must install NoMachine (Free Edition, for example, or any other NoMachine server) and make sure that 1) “Advertise this computer on the local network” is enabled on those machines. To do that, check the link just above. By default broadcasting is enabled. And 2) that your Player (the computer you are connecting from) is configured to show other computers on the LAN. To do that, open NoMachine Playersettings -> Security -> Check that you have not ticked the box “Don’t show other computers on the local network”. The default setting is to let you see other computers on the network.
Hi, we found that there is an incompatibility in the way the WebPlayer uses WebRTC, with the latest WebRTC released by Google.
They made a few changes to the WebRTC protocol and specifically changes to message IDs, that made our version incompatible.
We’ve fixed it and this is going to be released in the next maintenance, due in the next few days.
You can track the Trouble Report at this link: https://kb.nomachine.com/TR07T10566.Hi! We already tried it and it was ugly. But, we are working on something even better than this. And it will allow you to monitor a given machine, even monitoring the screen as you said 🙂
Can you submit a screenshot where the client shows SW encoding in the session?
Can you send us the logs of the 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!
https://kb.nomachine.com/DT07S00243
We are not aware of a similar issue. Is this on Ubuntu or something else?
Can you submit a screenshot where the client shows SW encoding?
Can you send us the logs of the 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!
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.