- This topic has 10 replies, 3 voices, and was last updated 23 hours, 59 minutes ago by
.
-
Posts
-
Hi,
after upgrading from NoMachine 8 to 9 (currently 9.0.188) on a Windows 11 host, the host becomes unreachable after a few days. When I login locally and look at the NoMachine server settings it says the server is still running fine, but trying to connect with nxplayer I get the error that there is not route to the host/ip. After restarting the NoMachine server on the Windows 11 host, everything looks as before, but now I can connect with nxplayer without problems. It works fine for some days, then again the connection fails with “no route to host <ip> found”. It worked flawlessly with NoMachine 8 before.
Is that problem known already?
cu,
Frank
We are not able to reproduce this. Can you send us the logs? 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. Thanks!
I could collect the logs when it happened and have sent a link to the requested email address where you can download them (they are 27MB, so I didn’t attached them to the email…). I hope the logs are helpful!
Happened again, I hope you are able to see sth. from the logs. Otherwise let me know if I should collect again!
I have this too – I connect in by Windows Virtual desktop as the machine is Win 11 Pro.
NX UI shows the server is running but you can’t connect to it.
If I restart NX from the UI I can then connect.
It started with NX 9
@Frank, we looked at the logs and noticed a similar problem to this bug report, https://www.nomachine.com/TR06W11409, which was fixed in 9.1, so if you have not updated to the latest version yet, please do so. If you are still seeing the same issue, yes, new logs with debug enabled would be useful. Please see the following instructions for how to set the debug level and gather logs, https://kb.nomachine.com/DT08U00298.
@CheltenhamSteve, it is not clear what steps you are taking to connect to the NoMachine server. What NoMachine product and version are you using on the device you are connecting from and what NoMachine product and version is installed on the target machine?@Britgirl I’m using 9.1.4 on the clients (Linux Mint and Windows 11) and the host (Windows 11 Pro). I also had the same problem on a Windows 10 host running 9.1.x.
I’m not relying on the host advertising on the network – I’ve got it set up as a specific connection.
I’ve put the server log into debug mode but sometimes it can go for a week or more without glitching.
“I’ve put the server log into debug mode but sometimes it can go for a week or more without glitching.”
Send in the logs if it happens again 🙂
Windows 11 machine was rebooted at approx 11:53 on Sunday 18 October and NX server had become unresponsive.
I tried to email the zip file of the logs but it bounced
so I sent it with just a link to the file.
Hi, thanks for the logs provided. We found an issue (not the same one as TR06W11409 mentioned above) that could cause a crash of the nxserver daemon process and we are already working on fix. You can use this link to monitor its status: https://kb.nomachine.com/TR10W11608.
You must be logged in to reply to this topic. Please login here.