Forum Replies Created
-
Posts
-
We’ve been able to reproduce it and have opened a Trouble Report which places it in the queue for fixing. Please sign up to the TR using ‘notify me’.
In the meantime we’ve been able to reproduce it and have opened a Trouble Report which places it in the queue for fixing. Please sign up to the TR using ‘notify me’.
See here: https://www.nomachine.com/AR02N00877
Hi, please avoid posting long excerpts of logs and use the attachment tool instead 🙂
From what you’ve written, your installation seems broken, license files were removed and permissions changed.
Please uninstall packages, remove /usr/NX directory and perform a clean installation.The NoMachine Free package doesn’t provide SSH support. SSH support is available in the NoMachine for the Enterprise range.
There is no workaround unfortunately. You will either have to switch back to the previous version of OpenSUSE or if that’s not possible you could try a different DE like XFCE4?
I just logged straight into the linux machine with one username/password.
Yes, with virtual Linux desktop which is available in Workstation. You can find it here: https://www.nomachine.com/download/linux&id=13
1. Is the additional cursor visible only in the NoMachine session or is it visible also on the physical Mac Book Pro?
2. Does it happen in a specific display mode only? (e.g. fit to window, resized)
3. Can you try to disable stream grabbing on the server side?
To do that, please set:
DisplayServerExtraOptions “-nostreamgrab” in node.cfg on server side
and restart NoMachine:
/etc/NX/nxserver –restart
Without this info it’s difficult for us to continue with the investigation.
Screen recording is possible via the session menu. Start a session, open the menu Ctrl-Alt-0 and select the ‘recording’ icon.
More details are available here: https://www.nomachine.com/DT07M00086
If you want to initiate session recording automatically, this is planned. You can see the Feature Request here: https://www.nomachine.com/FR03N03078
Session recording in web sessions is not available, but we are currently evaluating a possible implementation of this feature in web-based sessions.
NoMachine works with Gnome (and it works with many of the tens of Linux DE available ;-))
If you are using the free NoMachine on the remote computer, it allows one connection. The person sitting at that computer who lets you connect to it will be able to see what you are doing once they’ve authorized you.
https://www.nomachine.com/forums/topic/can-remote-host-see-what-im-doing#post-8287
Anywhere/Network has been rescheduled to fit in with some major changes that we are planning for version 6 (related to our product model).
First let’s clarify that NoMachine for Windows doesn’t support terminal server on Windows, so it’s not possible for multiple users to each connect to their own account at the same time. NoMachine free version supports one connection at a time to the remote desktop. Enterprise Desktop, on the other hand, allows unlimited connections and when multiple users connect at the same time, they are sharing the same desktop.
In both cases, if there is no local user (the person sitting in front of the desktop you are connecting to), then you will need to check the box “Require permission to let remote users interact with the desktop” in Security preferences of the server GUI (on the host you want to connect to). This is disabled by default. Checking the box means that users will connect in view only mode. Interaction can be enabled at a later time by the owner.
See the quick guide here:
https://www.nomachine.com/DT11M00106#3.2.We’ve opened a Trouble Report for this: https://www.nomachine.com/TR02O07604
The temporary workaround is to comment the keys (see TR link).
I don’t think elevating the severity will change the fact that the solution is to encode monitors in separate video streams due to the video encoders not supporting such high resolutions themselves. As Fra81 mentioned it’s a rather big task and one that is underway. Believe me, if there had been a quick fix, we would have already pointed it out in the TR 😉
Here is the Trouble Report for this bug: https://www.nomachine.com/TR04O07712
Please sign up to the ‘notify me’ tool to know when a fix has been released.