Britgirl

[Britgirl]

We have reproduced this same behaviour and will be opening a Trouble Report. When you are in session with enabled caps lock and then disable caps lock and move to another window (for example move from notepad to terminal ) caps lock will be locked.

A temporary workaround can be clicking outside of session and then proceed with disabling caps lock.

[Britgirl]

nxmac, we got your email with the set of missing logs and will update this topic soon. Thanks for your patience 🙂

p.s we don’t need logs for the other topic, please check that topic to see a possible workaround that worked for us.

[Britgirl]

I’m not sure what the problem is that you have with the software you’ve installed. It seems to me that your license has expired and for this reason you can only install up to a certain version of v6 updates. The same rule applies to v7 updates installed on top of v6 software. i.e it’s not possible to install updates of any release on top of software which has an expired subscription.

For version 6, once your subscription expired, updates were no longer possible and the software continued to run as expired software. So, if you had a subscription, let’s say purchased on December 21st, 2018 and it expired on December 21st, 2019, you would have been able to install updates which were released before your expiry. So, in this particular example, the maintenance of v6 which was 6.9.2 (Dec 17th, 2019) could have been installed. Any maintenance update which we released after the license expiry date of December 21st 2019 could not have been installed, but the software would continue to let you connect.

This model changed in version 7.

Pasting from the article in our KB:

Why renewing your NoMachine Server license is important
https://kb.nomachine.com/AR03D00365

Starting from version 7, it is necessary for subscriptions to be renewed in order to continue to use the software, and keep your NoMachine server(s) in a functional state. When your subscription period has expired, the software will stop working and connections will no longer be possible.

This applies to v7 licenses and later, and also v5/v6 licenses activated in v7 software.

 

[Britgirl]

Hi,

to be able to connect a computer which is not on your same LAN, you need to use the public IP address of the computer you want to access. Please check the following articles if you have not already done so:

How to connect over the Internet (enable UPnP to automatically configure port mapping)
https://kb.nomachine.com/AR10T01175

How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122

The External IP of the computer you want to access can be checked by its owner on whatismyip.com and then communicated to you.

If this doesn’t help, please send a screenshot of the error message you are receiving when you connect to the other person’s PC.

[Britgirl]

We don’t see many differences in your environment settings between the two. You could try editing /usr/NX/etc/node.cfg on the server side:

DefaultDesktopCommand "env XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share /usr/bin/startxfce4"

and connect again to your “headless” machine (on the server first stop X server and then sudo /etc/NX/nxserver --restart and then connect)

If the problem is still there, tell us what distro is and how you installed xfce.

[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.

[Author]

Posts