Forum Replies Created
-
Posts
-
What you sent us is from the player side.
192 192 2025-07-12 18:56:21 028.117 ClientSession: Failing reason is ‘No route to the network or to the host ‘172.xx.x.xxx’ was found. The issue could either be caused by a wrong server address or by a networking problem. Please verify your connection and try again.’.
On the server host you want to connect to (172.xx.x.xxx), go to the settings>server>security and set debug level 9, restart, reproduce and click take logs.
Please update to NoMachine 9, since the TR I linked in my previous post is now solved. If you still encounter the problem on v9, a new topic can be submitted. Thanks!
Can we see the logs from the server side machine? Go to Settings > Server > Security, set log level to 9, reproduce the problem, then “take logs “. For full instructions see this document: https://kb.nomachine.com/DT08U00298. Send us the complete file, you can either attach here or send directly to forum[at]nomachine[dot]com, making sure to reference the title of the topic as the subject of your email.
“I don’t even know what “an MDNS connection is” – Sorry, I was asking how you are connecting, i.e are you creating a connection or are you clicking the machine icon (pipe icon) to connect.
In any case, we still need logs with debug enabled on the server because the problem you have now is different to the original “connection reset” error. Please send the server logs and the player logs as described in the document I linked previously.
What is the best practice to add nodes created in inverse mode to nodes group “ndgr_XYZ” ?
The best practice is to use node commands on machine with installed CS
This local admin can’t create nodes group on ECS, managed by a dedicated admin, can he ?
The admin who is managing nodes of ECS cannot manage ECS groups.
Should only these 2 commands be used by ECS admin to addd nodes to nodes group ?
Yes
It is mandatory to use node_UUID ?
You can choose between uuid and node-name. When you manage nodes which are accessible from ECS you can also use ip:port. In your case nodes are behind firewall so you can only use uuid/node-name.
Hi mckaygerhard, we checked the code fragment he proposed, but there wasn’t any change. Can we ask you to submit logs? In Settings > Server > Security, set log level to 9 and restart the server. Reproduce the issue and then go back to the settings and click Take logs. Submit the file here or send directly to forum[at]nomachine[dot]com. Thanks!
We have opened a Trouble Report which you can monitor here: https://kb.nomachine.com/TR07W11459. Although your issue is a black screen, it’s caused by the same bug.
Your request is certainly a reasonable one though, so we’ll see how we can improve this aspect
Please use the following link to monitor the fix: https://kb.nomachine.com/TR07W11471.
We have opened a Trouble Report for this issue, please use the following link to monitor its status: https://kb.nomachine.com/TR07W11470.
You say it’s on the same LAN, so are you using an MDNS connection (a NoMachine host broadcast on LAN) ?
Can we see the logs from the Raspberry server? Go to Settings > Server > Security, set log level to 9, reproduce the problem, then “take logs “. For full instructions see this document: https://kb.nomachine.com/DT08U00298. Send us the complete file, you can either attach here or send directly to forum[at]nomachine[dot]com, making sure to reference the title of the topic as the subject of your email.
This is the Trouble Report which you can monitor: https://kb.nomachine.com/TR05W11324.
The issue looks like this Trouble Report, currently open: https://kb.nomachine.com/TR08R09811. Please use that link to monitor its status.
The Trouble Report was solved in the following software update: https://kb.nomachine.com/SU05W00266. Please update to NoMachine 9 if you’ve not done so already. Thanks.
Hello,
To help us diagnose the issue, could you please run the following commands on your system and send us the resulting output files?
systemctl –user status pulseaudio.* pipewire.* pipewire-pulse.* > systemctl_status.txt
pactl info > pactl_info.txt
pactl list sinks > pactl_sinks.txt
pactl list sources > pactl_sources.txtOnce you have these files, please compress them into a single archive (for example, audio_logs.zip) and attach it to your next message.
Thank you for your help—this information will allow us to investigate the problem more effectively.