Britgirl

[Britgirl]

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.

[Britgirl]

We’ve opened a Trouble Report for this: https://www.nomachine.com/TR02O07604

The temporary workaround is to comment the keys (see TR link).

[Britgirl]

Weird :-/ thanks for letting us know, we’ll do some investigating.

[Britgirl]

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 😉

[Britgirl]

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.

[Britgirl]

Check your inbox 🙂

[Britgirl]

If you have NoMachine virtual desktop sessions running you can do (via ssh):

sudo /etc/NX/nxserver --history | grep Connected

sudo /etc/NX/nxserver --terminate <session ID>

(We’re currently evaluating simpler nxserver commands).

Otherwise, a simple restart via ssh.

[Britgirl]

I’ll get the notify me checked. It’s weird because I received notification that you had updated this topic.

[Britgirl]

can you both check your inboxes please?

[Britgirl]

We’ll need to see the logs from both sides. Please follow the instructions you can find here: https://www.nomachine.com/DT07M00098

Then, zip them up and attach them to an email which you can send to forum[at]nomachine[dot]com

[Britgirl]

If you are installing NoMachine in a VM instance, please refer to https://www.nomachine.com/AR11E00489

“…for every virtual server instance of VMware that you wish to connect to, one subscription license file will be required. So if you have a server machine that will be providing 4 virtual instances by VMware, you will need 4 x NoMachine, or alternatively 4 X any of the Enterprise or Terminal Server subscriptions depending on your needs.”

 

Or have I misunderstood?

[Britgirl]

Hello,

thanks for the update. This would appear to be a licensed version with technical assistance enabled. Next time it might be better to contact your administrator and ask them to open a support ticket so that the team can investigate according to your entitlements 😉

[Britgirl]

Please make sure your Windows installation is up-to-date with any recent software updates. Also, use the latest NoMachine version. Then let us know if you continue to have the same issue.

[Britgirl]

Hi, we’ve reopened the Trouble Report. Please sign up to the notify me tool to know when a fix has been released. Thanks for reporting.

[Britgirl]

As I’ve just mentioned, we’ll need to send you a debug version because 1) the logs didn’t show anything useful and 2) we haven’t been able to reproduce the problem despite our tests since you submitted the logs. I take it that you have updated to our latest release?

[Author]

Posts