Britgirl

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

[Britgirl]

Take a look at the following topic: https://forum.nomachine.com/topic/user-for-instant-access#post-52574

I’ll post here for convenience. When you login with your MS account, the following formats are possible:

1) User Principal Name: @ – If you are getting an error, please tell us what error you are seeing when trying to promoted to authenticate on the target Windows machine

2) Down-Level Logon Name: \

3) Short format name, just ‘username’, domain is implicit.

A password is required, your Windows OS PIN is not supported. Please also take a look at the following article which explains in more detail: https://kb.nomachine.com/AR03S01118.

[Britgirl]

You attached the logs for the monitor issue with –eglcapture set to off which means the potential fix for the monitor issue didn’t help, right?

About the logs with –eglcapture enabled, from the logs we see it’s still loading the old library. So do a system reboot and grab new logs, please. Thanks once again.

[Britgirl]

In the meantime we have installed Trixie without any issues. Please, from a terminal on the raspberry device, run uname -m and show us the output, just so that we can be sure that you have the right package.

[Britgirl]

The logs don’t show evident issues within the software, the server closed cleanly. It could possibly be a network problem, but to make sure we need new logs. Set SessionLogClean 0 in the node.cfg file (/usr/NX/etc/node.cfg), reproduce and send the logs.

[Britgirl]

Hi, we’ve sent you a link to a new build. The instructions are the same as before 🙂

1) one set of logs with --eglcapture set to ‘no’ if you are still reproducing the monitor issue. Otherwise, no need for logs.

2) one set of logs with --eglcapture set to ‘yes’ and slowness reproduced.

[Britgirl]

On the macOS machine, you can use the sudo /etc/NX/nxserver --logrotate command in a terminal. Reproduce, then take fresh logs. (see 4.1. Clean-up All Logs in the link above).

[Author]

Posts