UltraVNC 1.2.4.0. Slow Screen Updating

[bbProg]

Hi,

After moving from Germany to the US, I have been experiencing slow response from the host only when connected from outside the network. It didn't happen while I was connected from within the network, so I can't say when exactly it started, but I didn't have this issue while living in Germany. In Germany I had DSL 100 Mbps and in the US cable 400 Mbps.

This happens only with UltraVNC. Connecting with TeamViewer or Chrome Remote Desktop does not show delays. I actually can see on Chrome or TeamViewer the action happening up to 10 seconds before it shows on UltraVNC - which means that there is no problem with the hardware.

The home PC is connected with WLAN at 433 Mbps.
Both host and remote version is 1.2.4.0 running on Windows 10 machines.
The same problem exists with version 1.2.2.3.

Any suggestions for improving the performance?

Barry

[Rudi De Vos]

Set manual the encoder on the viewer while connected.
Compression take time, some encoders can be used on 128k lines but are to slow for DSL

Try u2 ( video) encoder, most of the time i get a good reuslt with that one.

Viewer ->options->encoders

[bbProg]

Thanks for the promt reply.

the settings in the viewer were already on manual. I reset to defaults and it got a bit better, but still not good enough even with Video selected.

I don't know if it's connected, I am currently in Germay and when connected to another PC in Germany it's working well, this delay exists (for now) only with the PC in the US. I never tried to connect while being in the US but outside my network.

[Rudi De Vos]

Just did a test between Belgium and our webservers in the US.
OK, it's slower then having a local connection but compared to rdp i can't see a difference.

What's the ping of your server ?

Pinging uvnc.com [66.226.75.44] with 32 bytes of data:
Reply from 66.226.75.44: bytes=32 time=149ms TTL=118
Reply from 66.226.75.44: bytes=32 time=148ms TTL=118
Reply from 66.226.75.44: bytes=32 time=148ms TTL=118
Reply from 66.226.75.44: bytes=32 time=148ms TTL=118

Ping statistics for 66.226.75.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 148ms, Maximum = 149ms, Average = 148ms

[bbProg]

Pinging bbprog.ddns.net [68.173.36.128] with 32 bytes of data:
Reply from 68.173.36.128: bytes=32 time=118ms TTL=48
Reply from 68.173.36.128: bytes=32 time=111ms TTL=48
Reply from 68.173.36.128: bytes=32 time=108ms TTL=48
Reply from 68.173.36.128: bytes=32 time=107ms TTL=48

Ping statistics for 68.173.36.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 107ms, Maximum = 118ms, Average = 111ms

[Rudi De Vos]

Then we can exclude the network

Capture options could be the next.
server options->properties

Just set
[v]Poll fullscreen
[v]low accuracy
Legacy capture (*)Auto
Max Cpu 100

Try also with [v] desktopduplication on

[bbProg]

Thank you!
Everything was ticked as you mentioned except the Max CPU which was 40. I have changed it and it's now a bit better, but not as it used to be.
When I get back to the US I'll connect the PC again with a network cable and will check if it helps. That's the only change I can think of between the setting in Germany and now. Will post here when I have results.