hello DRC, no, I am just using "/opt/TurboVNC/bin/vncserver :1". Yes, my comment about adaptive resolutions is wrong :-/
TurboVNC 3.0 Server with TigerVNC-Viewer (64-bit) Version 1.8.0 does not show this problem. It is unlikely a network/firewall problem because for another user it works fine between the same two computers. Thanks and Best Regards, Felix DRC schrieb am Freitag, 29. Juli 2022 um 13:12:47 UTC+2: > Are you using ALR or any non-default server settings? I don't understand > your comment about adaptive resolutions. Remote Desktop should always > adapt the resolution, and what I observe is that, after connecting to > Windows, the remote desktop is the same size as the TurboVNC session. This > is true regardless of whether I connect to a Windows VM or a physical > Windows machine. > > Generally speaking, a "Rect too big" error is caused by a protocol > mismatch. The error could happen if the server sends an RFB message that > the viewer cannot handle, which is why the server and viewer negotiate > their capabilities beforehand. The error could also happen due to data > corruption on the network, which could be the result of a faulty firewall > or other intermediary. In order to diagnose the issue, I would first need > to reliably reproduce it. Then I would insert a lot of logging statements > into the server to determine exactly what it is trying to send whenever the > error occurs. > > Since I can't repro the issue, it would be a useful datapoint to determine > whether it occurs with a different VNC viewer, such as the TigerVNC Viewer. > -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/b263a77f-d4a0-49f6-8b18-288ededf9ecan%40googlegroups.com.
