Hi,
you might want to try adding /rfx for the win7 machines. Other than that there are certain limitations on total and per monitor resolutions that have been greatly extended since the days of win7. According to https://social.technet.microsoft.com/wiki/contents/articles/31983.remote-desktop-protocol-maximum-supported-resolutions.aspx you´re reaching the limit in your case. regards Armin On 7/30/19 1:36 PM, Andrew McGlashan via FreeRDP-devel wrote: > Hi, > > I'm hoping this mailing list is active.... been through all the issues > logged at https://github.com/FreeRDP/FreeRDP and can't find an answer. > > I remotely connect to multiple machines, recently I got a new 4K monitor > and am using that with a FHD monitor. > > If I connect to a Windows Server 2012 the /multimon works perfectly well. > > If I connect to a Windows 7 Pro, I am having problems with screen > resolution and allocation. > > > The following results in getting a screen resolution of 3840x2048 > instead of the full 3840x2160 > > xfreerdp /network:modem /drive:aaa,/mnt/tmpx \ > +clipboard +compression -wallpaper -themes /f \ > /v:win7.example.com:3390 /u:username > > If I use /multimon instead of /f expecting to use both monitors as two > separate displays for the RDP session, I get a total screen resolution > of 4096x2048 and Windows 7 shows only 1 screen in display settings. > > xfreerdp /network:modem /drive:aaa,/mnt/tmpx \ > +clipboard +compression -wallpaper -themes /multimon \ > /v:win7.example.com:3390 /u:username > > I am getting the actual screen resolution figures from Windows itself. > (Control Panel\All Control Panel Items\Display\Screen Resolution). > > > This is my current setup: > > $ xfreerdp /monitor-list > * [0] 3840x2160 +0+0 > [1] 1920x1080 +3840+0 > > In the past the Macbook Pro with a 2880x1800 screen was connecting to an > actual Windows Server 2012 at the site that now only has Windows 7 > machines available, but the Macbook Pro was seeing both screens and > using them properly just before a change to my client end setup. > > I am using the exact same command line on the new setup as I was with > the Macbook Pro. NB: Whilst the Macbook Pro has MacOs, I always use Linux. > > $ xfreerdp --version > This is FreeRDP version 1.1.0-beta1 (git n/a) > > > The Macbook Pro was running Devuan (Live USB) Ascii version and the new > setup is using MX Linux, but I'm pretty sure that MX Linux worked > properly until the first time that I adjusted the display alignment, > then the problems arose and I can no longer get proper dual screen > working for the Windows 7 connection; it still works perfectly well with > the Windows 2012 at the different site. > > > I can't see anything at the client end to clear to "start again" and > don't know which registry or other settings at the remote end might help > to be cleared so as to reset everything. > > Some details from "inxi -F" > > System: > Host: mx1 > Kernel: 4.19.0-5-amd64 x86_64 > bits: 64 > Desktop: Xfce 4.12.3 > Distro: MX-18.3_x64 Continuum May 26 2019 > > Machine: > Type: Desktop > System: Intel > product: NUC8i7HVK v: J71485-503 serial: <root required> > Mobo: Intel > model: NUC8i7HVB v: J68196-503 serial: <root required> > UEFI: Intel v: HNKBLi70.86A.0058.2019.0705.1646 > date: 07/05/2019 > > I just reconnected the Macbook Pro and it still works perfectly, showing > dual monitors on the Windows 7 Pro machine. Back on the new setup and > it still doesn't work; perhaps there is something I can reset or do to > fix it? > > How can I get proper dual screen support to work again for connections > to the Windows 7 Pro box? > > > Thanks and Kind Regards > AndrewM > > > _______________________________________________ > FreeRDP-devel mailing list > FreeRDP-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
