windows remote desktop connection doctor

Other Community

Skill notes

Background

Azure Virtual Desktop transport priority: UDP Shortpath > TCP > WebSocket. UDP Shortpath provides the best experience (lowest latency, supports UDP Multicast). When it fails, the client falls back to WebSocket over TCP 443 through the gateway, adding significant latency overhead. Direct PC connections use plain RDP over TCP 3389 (usually TLS-wrapped). They have no Connection Info panel, no gateway reachability tests, and no transport optimization step. For direct PC, the dominant failure modes are:

Step 1: Determine the Connection Type and Symptom

Before collecting evidence, identify which scenario you are diagnosing: Scenario · Key Characteristic · Primary Evidence Source AVD/WVD/W365 · User connects to a cloud desktop through a workspace/gateway · Connection Info panel, gateway health checks, UDP Shortpath logs Direct PC · User connects to a named PC by hostname or IP (e.g., a home workstation) · RDP protocol probe, Windows App log auth chain, Windows-side reboot events

Step 2: Collect Network Evidence

Gather evidence in parallel — do NOT make assumptions. Run the following checks simultaneously: 2A: Network Interfaces and Routing Look for: utun interfaces: Identify VPN/proxy TUN tunnels (ShadowRocket, Clash, Tailscale) Default route priority: Which interface handles default traffic

Step 3: Analyze Windows App Logs

This is the most critical step. Windows App logs contain transport negotiation details that no network-level test can reveal. Log location on macOS: Files are named: com.microsoft.rdc.macos_v<version>_<date>_<time>.log Important: Windows App log timestamps are UTC. The user's clock and Windows Event logs are usually local time. Convert all timestamps to a single timezone before building a timeline.

Step 4: Determine Root Cause

Based on collected evidence, identify the root cause category: Category A: VPN/Proxy Interference Evidence: Windows App source IP is 198.18.0.x, STUN/TURN routed through VPN, no UDP connections. Fix: Add DIRECT rules for AVD traffic in the proxy tool: Verify: Temporarily disable VPN/proxy, reconnect VDI, check if transport changes to UDP.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Windows · WSL
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Determine the Connection Type and Symptom

Before collecting evidence, identify which scenario you are diagnosing: Scenario · Key Characteristic · Primary Evidence Source AVD/WVD/W365 · User connects to a cloud desktop through a workspace/gateway · Connection Info panel, gateway health checks, UDP Shortpath logs Direct PC · User connects to a named PC by hostname or IP (e.g., a home workstation) · RDP protocol probe, Windows App log auth chain, Windows-side reboot events

02
Step 2: Collect Network Evidence

Gather evidence in parallel — do NOT make assumptions. Run the following checks simultaneously: 2A: Network Interfaces and Routing Look for: utun interfaces: Identify VPN/proxy TUN tunnels (ShadowRocket, Clash, Tailscale) Default route priority: Which interface handles default traffic

03
Step 3: Analyze Windows App Logs

This is the most critical step. Windows App logs contain transport negotiation details that no network-level test can reveal. Log location on macOS: Files are named: `com.microsoft.rdc.macos_v<version>_<date>_<time>.log` Important: Windows App log timestamps are UTC. The user's clock and Windows Event logs are usually local time. Convert all timestamps to a single timezone before building a timeline.

04
Step 4: Determine Root Cause

Based on collected evidence, identify the root cause category: Category A: VPN/Proxy Interference Evidence: Windows App source IP is `198.18.0.x`, STUN/TURN routed through VPN, no UDP connections. Fix: Add DIRECT rules for AVD traffic in the proxy tool: Verify: Temporarily disable VPN/proxy, reconnect VDI, check if transport changes to UDP.

05
Step 5: Verify Fix

After applying a fix, reconnect and verify the appropriate symptoms: For AVD/WVD/W365: Check Connection Info — Transport Protocol should show `UDP` or `UDP Multicast`. RTT should drop significantly (e.g., from 165ms to 40-60ms). Verify with lsof:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.