Britgirl

[Britgirl]

Got the logs, thanks Jesse. We’ll be taking a look and will let you know soon. Good to know the workaround temporarily solves the issue!

[Britgirl]

Tar.gz is the most universal package. Not all Linux distributions have a package manager which supports rpm or deb. So for those die-hard Linux users who want to use NoMachine on distros that we don’t officially support, or that doesn’t offer their own package manager, they can opt for the tar (Tiny Core and earlier versions of Slackware for example, Gentoo and Arch as well, https://kb.nomachine.com/AR03L00789). We don’t like to exclude people from trying the software just because they are not using one of the traditional distributions. Good luck with your search. Maybe in the future you’ll give us another chance.

[Britgirl]

Hi, it looks very similar to this known issue:

https://kb.nomachine.com/TR11W11619

Can you try the workaround there? We’d also be happy to take a look at the logs to check. Follow the instructions here: https://kb.nomachine.com/DT08U00298#1.1 and send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.

If the logs confirm the exact same problem, we’ll send you a fix to try.

[Britgirl]

Hi, please try again, it was a momentary glitch.

[Britgirl]

Hi, when you try connecting from the Macbook to the Linux server, do you see a black screen or a message? If it’s a message, can you show us a screenshot? Not seeing the local LAN connection of the Linux server on your macbook might be because maybe the macOS is not configured for LAN access in Privacy & Security in the system settings? I know you said it was working before, maybe something changed when you updated NoMachine to version 9.2.18? What version of macOS is it?

(P.s ideally you should update your legacy v7 Linux server to a more recent version. If you prefer to update first to v8, please contact us for a private link to the packages as they are no longer public.)

[Britgirl]

It’s probably better to split the topic now that you have resolved the problem of not being able to uninstall, and give it the correct title.  You asked in an earlier reply about whether we can make the process of installing the application on Linux a lot less convoluted. Well, we can say your install process was convoluted, no? Use the DEB the next time 😉

If you wish to continue the discussion about NoMachine not working correctly on your Pop!_OS COSMIC installation, let us know. Our own tests show that NoMachine sessions connect and work correctly. It would be useful to know what specific “action is not possible”. Do you mean you can see the desktop but can’t input anything?

[Britgirl]

Hi, this topic is similar to the one posted here https://forum.nomachine.com/topic/nomachine-main-ui-wont-open-on-windows. We have not been able to reproduce this issue with any of the multiple Windows systems with WSL enabled in our labs. It is likely due to a particular combination of tests and drivers that we have no way of verifying.  We are continuing to investigate, however, and we will update your topic with our findings.

 

[Britgirl]

ziggy, we are still investigating the logs that you submitted. However, could you try uninstalling NoMachine, removing all remaining permissions (delete, not just disable)  and start from a fresh installation? This will also clean up all old logs and
debugging will be easier if we need to ask you again for new logs.

xlear, your logs show the following:

13708 13344 2025-11-28 10:31:54 040.188 ClientSession: Failing reason is ‘Could not connect to the server.
Error is 10051: Network is unreachable’.

which suggests it’s a network issue and not a NoMachine issue. So please check your network before connecting and try again.

 

[Britgirl]

Hi, what is the desktop environment you are using? Can you send us the logs? You can extract them using the instructions here: https://kb.nomachine.com/https://kb.nomachine.com/DT08U00298#1.1. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, can you tell us what scaling settings are configured on the system?

[Britgirl]

Hi, are you able to send us the server-side logs so we can check them? You can extract them using the instructions here:
https://kb.nomachine.com/DT08U00298#1.1.

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.  Or you can upload them here. Thanks!

[Britgirl]

Thanks xlear, we received your logs.

[Britgirl]

Xlear, when that happens, click Save the connection logs and send that to us: attach it here or send via email to forum[at]nomachine[dot]com. Make sure you use the title of this topic as the subject of your email.

[Britgirl]

Hi,

adding an option to swap Control and Command modifiers on the remote desktop was implemented in 9.0.188. Are you using v9 on both client and server sides?

The new option is added in connection menu -> Input. You can see a screenshot in “Guide to the Functionality in the Menu Panel on Windows”. The label is “Map Ctrl to Cmd and Win to Ctrl”. When this option is not enabled, instead, the user has to use the remote modifier for applying keyboard shortcuts inside the NoMachine session.

https://kb.nomachine.com/DT08U00291#3

Does this help?

[Britgirl]

Hi, the variable is correct, but if you uninstalled, it’s necessary to restart the desktop manager, so either logout and log back in, or reboot your machine.

[Author]

Posts