- This topic has 5 replies, 3 voices, and was last updated 2 years, 6 months ago by
.
-
Posts
-
NoMachine version: 7.2.9_1
Windows host: Windows 10
Connect machine: Windows 10, Windows 11
I have installed/uninstalled NoMachine many times in host system. Attached is the log.
Thanks, for any help.
From the logs you attached we can see that you have a huge screen size (server side):
Info: Using screen size 8960x3600and there is not enough memory to allocate the frame buffer.
13256 6708 15:45:08 034.568 MirrorPoller: ERROR! Can't allocate 129024000 bytes for the texture dataWhen we release version 8, we will release Windows packages explicitly for 64-bit. It could be what you need. Until then, I suggest you reduce the size of the server-side monitor.
We have the same behavior with Windows but only when running NoMachine as a specific user. If we run NoMachine as any other user it works fine and does not immediately disconnect. I’ve looked though the logs but we don’t have any screen size errors.
I’ve tried reinstalling different versions but that specific user account always disconnects immediately after connecting. Is there some user specific configuration that does not get cleared during uninstall? Initially it was working on that user account until updating NoMachine. But now it does not even work when we reinstall the old version.
dsat2002, your issue appears to be a different one. Please open a separate topic including details of NoMachine products, versions (client and server), OS and version (client side and server side) and steps to reproduce. Screenshots of any error dialogs you see should be attached.
Logs from after you have reproduced the problem would also be useful. On the Windows server machine, please enable logs as described in these instructions and then send them to us at forum[at]nomachine[dot]com making sure that you include the title of your new topic. Thanks!
This topic was marked as solved, you can't post.