Britgirl

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

[Britgirl]

Try sending them to forum[at]nomachine[dot]com.

[Britgirl]

Hi, this looks like you installed the wrong package. You have 86x-64 architecture which means you require 64-bit packages.
It’s the second button here: https://download.nomachine.com/download/?id=1&platform=linux.

[Britgirl]

I’m happy to do that, but I don’t see where the setting is to enable debug, even if I can find the Take Logs.

Apologies I should have pointed you to the instructions (https://kb.nomachine.com/DT08U00298?s=logs#1.1).

On the Mac Mini, where you find the Take logs button in Server settings, there should be a level you can set as well. Set it to level 9, then restart the server (see the attached image). Pasting in the first few steps that apply to you from the document mentioned above.

Step 1 – Open the UI on the server host -> Settings -> Server -> Security

Step 2 – Scroll down the Security panel till the end to find section ‘Server logs’. Set there the log level as requested by the Support Team. Restarting the server is requested to make change effective, this will terminate all sessions. If this is not an option, use the manual procedure from command line.

Step 3 – Reproduce the problem.

Step 4 – Click on the ‘Take logs’ button: you will be requested to provide username and password of the administrator. Logs will be saved in a .zip archive.

However, in that context, is it safe to discard logs that are older than that?

Yes.

it is worth noting that I’m finding both Windows and Linux clients are able to discover this machine as active.

So you can see the Mac Mini when you are on the Windows and Linux clients, but you cannot connect from either?

[Britgirl]

A quick update on the investigation, thanks for your patience so far. 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’ll continue to investigate, however, but we’ll close this topic for now. Should we have something to report, we will provide an update here.

[Britgirl]

The key you tried to add in player.cfg is not supported.

On the NoMachine server host, it’s possible to enable a key in the node.cfg file to configure the packet prioritization flag for
NoMachine data traffic for data from server to client:

#
# Set the DS (Differentiated Services) 8-bit field, previously known
# as ToS (Type of Service), at the IP network layer. Valid values are
# numbers from 0 to 255 in decimal or hexadecimal format (0x00-0xff).
# The six most significant bits should be set to the DSCP values recom-
# mended by RFC-2597 and RFC-2598 (e.g. use 72 or 0x48 for DSCP Class
# AF21). The two least significative bits should be set to 0. It is
# also possible to use the obsolete ToS flags (e.g. 16 or 0x10 for the
# LOWDELAY behaviour).
#
# ProxyPacketPriority 0x48

Remove the pre-pending # from the key name.

[Britgirl]

The logs showed that there is no FullHD in use, but 3840×1080 (so height is 1080 but the width is 1920*2) hence why SW encoding is being used given that for resolutions higher than 4K, hardware encoding is disabled. Work has already started to remove this limitation.

[Author]

Posts