November 12, 2020 at 09:17 #30307
I think the issue is related to the remote machine’s Power & Sleep setting.
The remote PC Screen is set to turn off after 3 hours.
If it has been 3 hours and the screen is off when I connect, NoMachine displays the desktop, but mouse and keyboard input do not respond.
After closing NoMachine and reconnecting, mouse and keyboard inputs work as expected.
Remote & local OS: Windows 10
NoMachine Version: 6.12.3 free version
Connecting to a physical display on remote machine (3 displays are connected)
Attachments:November 19, 2020 at 09:43 #30446
We haven’t been able to reproduce this at all. Please send us a screenshot from the Advanced Power Settings plus logs from the affected Windows server host. Please see here for instructions on where to find logs.
Submit everything to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!November 19, 2020 at 16:08 #30450
I have submitted the log files as requested.
And, I made a video of all the Advanced Power Settings and sent that in an email too.
Here is some more info on this behavior:
- When connecting the first time, I *DO* have mouse and keyboard control of the remote (server) PC, but I cannot see it. I only see a static image of the remote desktop. When double click on a desktop icon, nothing happens locally. But, when I quit NoMachine and connect the second time, the program that I double clicked on is open and running.
- On the local machine, when I connect the first time, I see the remote (server) PC desktop, but when I move the mouse, the remote (server) mouse seems to just drift and not follow my local mouse cursor. (I have show server mouse icon enabled).
- The remote (server) PC has 3 screens attached.
- The remote (server) PC is configured to login to a standard user (non-admin) account automatically at boot. This is set by running the netplwiz utility:
Then, in the User Accounts dialog box, click the account you want to automatically log on to.
Then, clear the ‘Users Must Enter A User Name And Password To Use This Computer’ check box.
Then, Click OK
Hope that helps. Thanks!November 19, 2020 at 16:08 #30451
Another user that remotes into the same PC is on Mac and also sees the same issue when first connecting.December 7, 2020 at 14:55 #30669
Any more progress looking into this issue?
Anything more info or details you want from me?December 7, 2020 at 17:49 #30675
We haven’t been able to reproduce the problem unfortunately (although we are still trying). We are currently making some changes to initialization of desktop duplication which we use for capturing screen, and we think this will help your case when these get released, most likely in version 7 onwards.December 8, 2020 at 08:45 #30676
Thanks. Any idea when I can expect to see version 7?December 8, 2020 at 16:04 #30684BilbotineKeymaster
I don’t have a date, but the release of version 7 should happen in the very near future.January 13, 2021 at 08:50 #31242
Update with version 7:
Version 7 seems to have improved things. I don’t see this issue every time anymore, but I do still see the same issue.
So, it seems more random now.
Sometimes first connection when the PC screen is sleeping, NoMachine works fine.
Other times, same thing happens and I need to disconnect and reconnect. After reconnecting, all works great.
So, that is an improvement. But, it might be harder to debug now because the issue seems more random.
On version 6, it happened every time the remote PC’s screen timeout had been reached and the screen was sleeping.January 18, 2021 at 16:03 #31337
If you can send us logs when it does happen, this would be useful.
You must be logged in to reply to this topic.