Share via

Virtual Desktop re connection issue

Deepak Kumar 145 Reputation points
2026-05-25T13:25:52.8866667+00:00

Hi, How to fix Sw-02 AVD issue as its showing Your connection round trip time is high. You may experience issues in SW-VM 02. but in RBKC is good. please help to enable UDP and “Based on the network traces we’ve analyzed so far, we observed that the AVD machine with IP address 10.0.0.4 is sending reset packets to the 172.26.36.50 IP, as seen in the packet capture.”

[Window Title] Remote Desktop

 

[Content] - RBKC-0 - UK South Your connection round trip time is high. You may experience issues. Multipath (UDP/WebSocket) is enabled.

 

[^] Hide details  [Send Diagnostics] [Disconnect] [OK]

 

[Expanded Information] Timestamp (UTC): 2026-05-25T12:15:25.7096286Z Activity ID: 97f64fc8-6d4f-4f31-a7a3-5acc426a0000

 

[Client details] Client version: 1.2.7152.0 (x64) Local OS: Microsoft Windows 11 Business x64 (10.0, Build 26200)

 

[Network details] Transport protocol: UDP - Multipath Round-trip time: 200 ms Available bandwidth: Greater than 151 Mbps Frame rate: 0 FPS

 

[Graphics details] Codecs used: AVC; RemoteFX Text; Cache Client compatibility:  Media Foundation: Yes GPU Presentation: Yes AVC: CPU; GPU HEVC: GPU

 

[Remote computer details] Remote session type: Remote desktop Gateway name: Not in use Gateway logon method: Not in use Remote computer: rbkc-avd-0 Identity verification method: Server Certificate (View certificate)

-

Remote Desktop

 

[Content] - SW VM 02 , location - UK West Your connection round trip time is high. You may experience issues.

 

[^] Hide details  [Send Diagnostics] [Disconnect] [OK]

 

[Expanded Information] Timestamp (UTC): 2026-05-25T11:25:37.1500479Z Activity ID: ca6e29db-0285-418e-85f9-e51421b20000

 

[Client details] Client version: 1.2.7152.0 (x64) Local OS: Microsoft Windows 11 Business x64 (10.0, Build 26200)

 

[Network details] Transport protocol: WebSocket Round-trip time: 320 ms Available bandwidth: 7.06 Mbps Frame rate: 0 FPS

 

[Graphics details] Codecs used: AVC; RemoteFX Text; Cache Client compatibility:  Media Foundation: Yes GPU Presentation: Yes AVC: CPU; GPU HEVC: GPU

 

[Remote computer details] Remote session type: Remote desktop Gateway name: rdgateway-host-blue-c226-seas-r1.wvd.microsoft.com Gateway logon method: Azure Active Directory Remote computer: sw-vm-02 Identity verification method: Server Certificate (View certificate)









Windows for business | Windows Server | User experience | Remote desktop services and terminal services

1 answer

Sort by: Most helpful
  1. HLBui 6,755 Reputation points Independent Advisor
    2026-05-25T18:02:46.8633333+00:00

    Hi Deepak Kumar

    From what I can see, the main difference between RBKC and SW-VM02 is that RBKC is happily running over UDP multipath, while SW-VM02 is falling back to WebSocket, which explains the higher round-trip time and degraded performance. The packet captures showing resets from 10.0.0.4 to 172.26.36.50 suggest that UDP traffic isn’t being allowed through somewhere along the path, so the session defaults to TCP/WebSocket. That’s why you’re seeing 320 ms latency and low bandwidth on SW-VM02 compared to the 200 ms and higher throughput on RBKC.

    The fix usually comes down to making sure UDP 3478–3481 is open end-to-end (client, firewall, NSG, and any intermediate appliance). Double-check that your NSGs and firewalls in UK West are aligned with the RBKC setup in UK South. Also, confirm that the AVD session host in SW-VM02 has the right outbound rules and isn’t blocking UDP itself. Once UDP is properly enabled, the client should negotiate multipath again, and you’ll see the round-trip time drop significantly. If you still see resets after that, I’d recommend running a targeted trace on those ports to confirm whether the block is happening at the network edge or inside the VM.

    So in short: align the UDP rules with RBKC, validate NSG/firewall configs, and re-test the session. That should get SW-VM02 back on track.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.