Britgirl

[Britgirl]

Good to know 🙂

[Britgirl]

Hi, you mention “take back control”. If your question is related to a sharing desktop scenario with another user and you find yourself in the situation that you want to disconnect any user which is connected to your computer, go to !M in the system tray and select to disconnect a specific user or all users. You can read more about this here:

https://kb.nomachine.com/DT07S00239#5.1

Additionally, something to consider about NoMachine in desktop sharing scenarios is that by default it gives priority to keyboard and input events from the local user logged-in to the remote computer over input generated by a user connected remotely via NoMachine. This adds 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.

Does this answer your question?

About the topics from a while back for Linux set-ups, they are rather outdated now and were closed because the users didn’t get back to us 🙂

[Britgirl]

is it possible to implement this feature?

This is exactly what we are evaluating 😉

Edited 17/4/2023: we will be adding the possibility to specify multiple IP addresses for the NXdListenAddress key.

[Britgirl]

NXdListenAddress is working only for single IP and not multiple entries. The correct syntax to use is NXdListenAddress “ipaddress” as indicated in the cfg templates, using without “” can create issues on some systems. Did you restart nxserver after changing that NXdListenAddress?

We confirm that NXdListenAddress will be correctly shown in the MDNS broadcasts, but NXdListenAddress does not show correct information in the Server Settings/ Status panel. This will need further investigation.

 

[Britgirl]

Hi, there was a problem with the upload of your images, so if you could send these directly to forum[at]nomachine[dot]com I can make sure they are uploaded correctly. Please make sure one of the images you upload show what it is you are seeing in the NoMachine session window, so we can understand better.

First we need to rule out potential issues with compression, so you should increase the quality with the slider in the Connection Menu. Connect to your NoMachine Linux machine (the server), Ctrl-Alt-0 -> Display -> Change Settings -> Move the slider to the right. Does this improve image quality?

Again, in the connection menu, can you make sure “Scale to window” option is disabled in the Display panel of the menu?

More about the Connection Menu and the Display Settings is available here: https://kb.nomachine.com/DT06S00218#5.7

[Britgirl]

We are not aware of white screen issues when HW encoding is disabled on a NoMachine for Mac server, nor garbled screen. We would require:

1. logs of the server side when you encounter the blank screen issue. To extract logs of the affected server, please follow the instructions here: https://kb.nomachine.com/DT07S00244

2. screenshot or video of the garbled display issue

Please contact us via the website if you require a link to download an earlier version (footer of website -> contact us -> general enquiries).

[Britgirl]

Try the workaround here: https://forums.nomachine.com/topic/server-permanently-has-no-audio-even-out-of-session-and-service-stopped#post-42260

[Britgirl]

Please submit a screenshot of what you see when connecting from computer B to computer A.

[Britgirl]

There is a Trouble Report for this issue which was opened in November.

Audio doesn’t work on Ubuntu 22.04 with PipeWire installed
https://kb.nomachine.com/TR11T10696

The workaround is available in the TR, but I will paste it here for reference. On the server side:

edit `/usr/NX/etc/node.cfg and set:

AudioInterface pulseaudio`

and restart nxserver:

sudo /etc/NX/nxserver --restart

[Britgirl]

We have opened a Trouble Report which can be monitored using the following link:

https://kb.nomachine.com/TR02T10471

We reproduced the same issue on Debian and also with the following envs:

sddm + gnome 43
gdm 43 + xfce4

On the other hand gdm + gnome 43 did not show the error.

[Britgirl]

Hi, sorry for the delay in giving you some feedback. Unfortunately there is no temporary workaround. In the meantime, we have opened a Trouble Report for this issue so that you can track its fix. This topic will now be closed.

https://www.nomachine.com/TR12T10728

[Britgirl]

Is that a screenshot from the computer you are connecting to?

When user John disconnects, what is seen? Can you show a screenshot of what is visible when John disconnects?

[Britgirl]

Please contact us via the website for this request. In the footer, select Contact Us and then select General Enquiries.

[Britgirl]

You can send any attachments to forum[at]nomachine[dot]com. Make sure you use the title of this topic as the subject of your email. Thanks!

[Britgirl]

The link we sent in the email to you to download is for a package that contains a patch. We were interested in knowing if it fixes the issue completely. If you get a chance to test it, please do 🙂

[Author]

Posts