Skip to content

Commit f61336a

Browse files
committed
Adressing blocking issues
1 parent 804957b commit f61336a

File tree

6 files changed

+5
-5
lines changed

6 files changed

+5
-5
lines changed

articles/virtual-desktop/rdp-shortpath.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -195,37 +195,37 @@ Here are some example scenarios to show how connections are evaluated to decide
195195

196196
A UDP connection can only be established between the client device and the session host over a public network (internet). A direct connection, such as a VPN, is not available.
197197

198-
:::image type="content" source="media/rdp-shortpath-scenario-1.png" alt-text="RDP Shortpath scenario 1.":::
198+
:::image type="content" source="media/rdp-shortpath/rdp-shortpath-scenario-1.png" alt-text="Diagram that shows RDP Shortpath for public networks is used." border="false":::
199199

200200
### Scenario 2
201201

202202
A UDP connection can be established between the client device and the session host over a public network or over a direct VPN connection, but RDP Shortpath for managed networks is not enabled. When the client initiates the connection, the ICE/STUN protocol can see multiple routes and will evaluate each route and choose the one with the lowest latency.
203203

204204
In this example, a UDP connection using RDP Shortpath for public networks over the direct VPN connection will be made as it has the lowest latency, as shown by the green line.
205205

206-
:::image type="content" source="media/rdp-shortpath-scenario-2.png" alt-text="RDP Shortpath scenario 2.":::
206+
:::image type="content" source="media/rdp-shortpath/rdp-shortpath-scenario-2.png" alt-text="Diagram that shows a UDP connection using RDP Shortpath for public networks over the direct VPN connection will be made as it has the lowest latency." border="false":::
207207

208208
### Scenario 3
209209

210210
Both RDP Shortpath for public networks and managed networks are enabled. A UDP connection can be established between the client device and the session host over a public network or over a direct VPN connection. When the client initiates the connection, there are simultaneous attempts to connect using RDP Shortpath for managed networks through port 3390 (by default) and RDP Shortpath for public networks through the ICE/STUN protocol. The first-found algorithm will be used and the user will use whichever connection gets established first for that session.
211211

212212
Since going over a public network has additional steps, for example a NAT device, a load balancer, or a STUN server, it is likely that the first-found algorithm will select the connection using RDP Shortpath for managed networks and be established first.
213213

214-
:::image type="content" source="media/rdp-shortpath-scenario-3.png" alt-text="RDP Shortpath scenario 3.":::
214+
:::image type="content" source="media/rdp-shortpath/rdp-shortpath-scenario-3.png" alt-text="Diagram that shows the first-found algorithm will select the connection using RDP Shortpath for managed networks and be established first." border="false":::
215215

216216
### Scenario 4
217217

218218
A UDP connection can be established between the client device and the session host over a public network or over a direct VPN connection, but RDP Shortpath for managed networks is not enabled. To prevent ICE/STUN from using a particular route, an admin can block one of the routes for UDP traffic. Blocking a route would ensure the remaining path is always used.
219219

220220
In this example, UDP is blocked on the direct VPN connection and the ICE/STUN protocol establishes a connection over the public network.
221221

222-
:::image type="content" source="media/rdp-shortpath-scenario-4.png" alt-text="RDP Shortpath scenario 4.":::
222+
:::image type="content" source="media/rdp-shortpath/rdp-shortpath-scenario-4.png" alt-text="Diagram that shows UDP is blocked on the direct VPN connection and the ICE/STUN protocol establishes a connection over the public network." border="false":::
223223

224224
### Scenario 5
225225

226226
Both RDP Shortpath for public networks and managed networks are configured, however a UDP connection could not be established. In this instance, RDP Shortpath will fail and the connection will fall back to TCP-based reverse connect transport.
227227

228-
:::image type="content" source="media/rdp-shortpath-scenario-5.png" alt-text="RDP Shortpath scenario 5.":::
228+
:::image type="content" source="media/rdp-shortpath/rdp-shortpath-scenario-5.png" alt-text="Diagram that shows a UDP connection could not be established. In this instance, RDP Shortpath will fail and the connection will fall back to TCP-based reverse connect transport." border="false":::
229229

230230
## Next steps
231231

0 commit comments

Comments
 (0)