- This topic has 1 reply, 2 voices, and was last updated 1 year, 3 months ago by
.
-
Posts
-
NoMachine – 8.8.1
Windows 10 22H2
After the machine is rebooted, the server service is running (TCP port 4000 open on machine) but I can’t connect…
If I do nxserver –restart on the machine, then I can connect…
Log entries after reboot of interest:
11 13:45:24 984.638 NXSERVER WARNING! NXRedis: command line ‘command=hmset,service=db,key=debugusers,field=NT AUTHORITY\SYSTEM,value=NT AUTHORITY\SYSTEM\n’ cannot contain spaces.
7584 7584 2023-08-11 13:45:24 984.638 NXSERVER WARNING! NXRedis: Sending command ‘command=hmset,service=db,key=debugusers,field=NT AUTHORITY\SYSTEM,value=NT AUTHORITY\SYSTEM\n’ aborted.
7808 7808 2023-08-11 13:46:16 764.158 NXNODE WARNING! NXRunner –monitor PID handle closed.
7808 7808 2023-08-11 13:46:16 764.158 NXNODE ERROR! nxexec –monitor failed to start.
7808 7808 2023-08-11 13:46:18 826.588 NXNODE ERROR! Timeout while waiting data on handlers: NXLocalSession::callbackIfLogoutOrLockScreenNeeded
7808 7808 2023-08-11 13:46:18 826.588 NXNODE ERROR! Did not receive answer if we should logout or lock screen.So, I created a task scheduler job to run 1 minute after the machine starts up… this job runs nxserver –restart
And that works around the problem… Why is the additional restart of nxserver necessary?
Hi, we are unable to reproduce it. Can you enable debug on the affected Windows machine, restart Windows, connect, and if the connection fails, collect logs and share them with us. We would also need the logs from the Player which cannot connect. Please follow the instructions here to enable debug: https://kb.nomachine.com/DT07S00243 (first through to fourth steps). Submit the logs to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.