Is it getting confused because the clients primary display is 1920×1080? (as I said, if the connection is interrupted at all, it changes back to 1920×1080, and then I need to manually change it back to 2560×1600). I don’t understand why it won’t remember what display to open on, and what resolution it was using for a connection. It actually appears to be changing the server resolution, despite my startup option to “Don’t resize the remote display”, as if I open a spreadsheet, and then change to 2560×1600, it definitely updates to display more rows and columns. If the connection is interrupted at any point, it will revert to 1920×1080.

I must then edit the settings and change it to 2560×1600. What it then displays on my 4K display is the remote desktop, at 1920×1080 resolution. (why doesn’t it remember which screen it was last used on, or at least open on the same screen as the NoMachine app window? This is basic stuff.) As soon as the connection window opens, I drag that to the 4K display, and maximize it. It opens the connection window on the primary 1920×1080 display.

When I connect to the server, I choose: “ Show the remote desktop at it’s resolution using the scrollbars“, and “ Don’t resize the remote display“. NoMachine 7.3.2īefore connecting, I drag the NoMachine application window to the secondary 4K display Server is Linux mint 19.3, fully up to date.

Nomachine fit to screen