- This topic has 4 replies, 2 voices, and was last updated 7 months, 1 week ago by
.
-
Posts
-
On my old system I had no problems connecting with NoMachine to a VM running Windows 10. Got a new system and wanted to try the same thing but can’t get it to work. The Windows VM is running in Virtualbox 7 which runs on Ubuntu 23.10. I’m connecting from a Chromebook using the Android app.
The NoMachine client connects to the remote machine but generates a blank (white) screen. I disabled hardware acceleration etcetera in the NoMachine server and tried again. The client connects alright but this time it generates a black screen. As far as I can gather from the server logs, the NoMachine server tries to change the resolution on the remote machine to 1980×1080 but then fails to generate a display.
I have tried setting a fixed resolution on the remote machine as well as in Virtualbox. That both works fine but as soon as I tried connecting the NoMachine server still tries to reset the resolution on the remote machine. After disconnecting the resolution on the server is reset to maximum resolution, apparently overriding the windows 10 and VM settings. I have tried again, this time also setting a custom resolution on the client, same result. So I am out of options now :-).
I switched to chrome remote desktop for now and that worked without a problem. But I prefer using NoMachine for better functionality and it’s just simply annoying using NoMachine for all my other remote connections and a different application just for this one.
Server logs are attached.
Hi, are you able to send us the complete server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
This topic was marked as solved, you can't post.