Britgirl

[Britgirl]

Screen blanking is supported in all products. We are not aware of screen blanking issues when connecting to a physical desktop on XFCE. Does it also not blank screen from the !M icon of the system tray? (Desktop shared > Blank physical screen). Can you send the us the logs of the server host? Reproduce the issue again, then on the server host, go to the Server settings > Security > scroll down and click Take logs). You can attach them here or if you prefer send direct to forum[at]nomachine[dot]com. Thanks.

[Britgirl]

Hi,

from what you’ve written it seems you are activating screen blanking on the wrong side. Screen blanking blanks the screen of the target computer you are connecting to. So, in your case, you have two Windows computers, let’s call them “A”, the computer you are connecting from (the “client”). And “B” the machine you are connecting to (the “server”). This means that to activate screen blanking, you must configure machine B to blank the screen.

You have two choices. You can either configuring the ‘Server settings’ on machine B by enabling the box “Blank the physical screen when somebody connects” (Go to Server settings of Machine B > Security > tick the box ‘Blank the physical screen when somebody connects’. Or you can blank the screen during the session from the !M icon on the target desktop: i) start your NoMachine connection con A, ii) login to B with your system credentials, iii) go to the !M icon of the system tray on machine B, iv) click ‘Desktop shared’ and then toggle ‘Blank physical screen’.

[Britgirl]

We were able to report the issue. You can track the status of the fix using this link here: https://kb.nomachine.com/TR02X11712.
Thanks.

[Britgirl]

Unfortunately, there’s not much more we can debug. Although we would appreciate knowing if the the monitor issue disappeared when you set --eglcapture to no using the last package we provided.

[Britgirl]

Do you mean how to switch between running local applications, like Cmd+Tab?

[Britgirl]

Hi, first let’s explain how the resize works. When the resize remote display is enabled, the remote desktop and the local window geometries are always synchronized. If the remote desktop changes its geometry, the client adapts the window size. When the client can’t fulfill a request to change the window size (usually, because the size is bigger than the client monitor), since the server has priority over its resolution (i.e. the client can’t “force” it back), then the mode automatically switches to viewport mode.

Now, it’s not clear to us what is happening when the “session times out due to inactivity” – we are happy to check the logs and that will let us also check the sequence of events occurring when you encounter the error. However, the technical behaviour is the one explained above, it is exactly how resize works when giving priority to remote desktop resolution.

We do have a Trouble Report open which has a workaround which you could try. Basically, the slider setting is ignored when disconnecting and connecting again to the same desktop. We are not sure if this is your case, https://kb.nomachine.com/TR07W11470.

To get the logs from the macOS client, reproduce the problem first, then, still on the client, go to Settings -> Player -> Security and ‘Take logs’.

[Britgirl]

Good to know 🙂

[Britgirl]

Hi, can you send us the logs from both client and server sides?
You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298. You can attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hello,

can you follow the instructions here:

How can I send Ctrl+Alt+Delete to a remote desktop?
https://kb.nomachine.com/AR02L00784

and if there is something that is not working as described there, please tell us?

[Britgirl]

Hi,

Local network connections don’t save a file in Documents\NoMachine, because of the ephemeral nature of automatic server discovery e.g., a machine might be temporarily unavailable or change its local address, and so on. Local server connections are stored in a temporary cache, where the cached connection files keep user preferences, but automatically update the server address and protocol information.

You have two options:

i) From the Windows player, create a new connection file manually and set the local LAN server’s IP in the Host field. The “Direct connection over the Internet” description that you see there might be misleading you. Creating a connection this way is not limited to WAN addresses only. Choosing this way to connect is useful only if the server IP doesn’t change.

ii) From the Windows player, in the Machines panel, edit the connection you want to launch automatically (right click on the connection icon), select Info in the left menu, copy the UUID visible in the Software group on the right, and look for the cached NXS file: %USERPROFILE%\.nx\cache\.nxs. Note however that when the system starts, the client has not yet received the broadcasted server address, so the one stored in the cache could be old and the connection may fail. Consider giving the Mac server a static LAN IP (in such a case, solution 1 would be easier).

[Britgirl]

It sounds like the macOS permissions are preventing you from interacting with desktop. Go to Accessibility and Screen Recording to check they are toggled on. If they are, remove NoMachine from the permission lists and add it again. Then go back to Server settings and restart the NoMachine server.

[Britgirl]

Hi, this time it’s the right package 🙂

You attached the logs with --eglcapture set to yes only. Does that mean that when you set the –eglcapture to no, you no longer reproduce the monitor issue?

Logs from the --eglcapture set to yes show that the slowness is caused by the drivers and not nomachine. Please try adding DisplayServerExtraOptions "-gpu 1" in the server’s node.cfg file and tell us if it makes any difference.

[Britgirl]

Hi, the client-side logs you submitted show that you are using version 8. Please try updating to the latest v9 on both the client and server sides and tell us if you can reproduce the issue. If you do, we will need to see logs from both sides. Please follow the instructions here: https://kb.nomachine.com/DT08U00298. For the client side logs, please refer to Chapter 1.2 of the same document.

[Britgirl]

Hi, so we checked the logs and there is no issue in the software, rather a broken connection caused by something in your network:

client:

8512 19344 2026-02-12 14:14:49 607.839 ProxySession/ProxySession: 
ERROR! Connection with the remote peer broken.
Error: Connection with the remote peer broken.
Error: Error is 5, 'Input/output error'.

server:

32294 22031 2026-02-12 14:14:50 060.364 ProxySession/ProxySession: 
ERROR! Connection with the remote peer broken.
Error: Connection with the remote peer broken.
Error: Error is 32, 'Broken pipe'.

[Britgirl]

Check your inbox. I’m sending you the download link again, it seems that you are still installing the earlier package we sent you? Remember to reboot the machine after installing. After which you can also add this to the node.cfg file on the target machine, DisplayServerExtraOptions "-gpu 1". This is a new key, not yet enabled by default, which we’ve added and it activates HW acceleration for some operations. It would be interesting to know if there is any difference.

[Author]

Posts