![windows server 2016 remote desktop slow windows server 2016 remote desktop slow](https://www.stephenwagner.com/wp-content/uploads/2020/03/microsoft-remote-desktop-services-1-1280x720.png)
![windows server 2016 remote desktop slow windows server 2016 remote desktop slow](https://venturebeat.com/wp-content/uploads/2020/06/TLOUPII_Review_Screenshot_08-Copy.jpg)
Next, on the perimeter firewall (the setting most people miss) be sure to include port 3391 UDP inbound (as well as leaving port 443 TCP in place), to your Gateway server.
Windows server 2016 remote desktop slow windows#
Step-by-step instructionsįirst, ensure that you have the rules enabled on the Windows Server(s) that hosts your Gateway role. Turning UDP on, however, should enable a superb connection and video experience for compatible RDP clients, as well as RemoteFX, if your setup supports it. The new protocol is much more efficient than RPC over HTTP, but of course if you don’t enable the new option, you would probably not notice, since RPC over HTTP will continue to work also (it is supported for legacy clients). But WS 2012/R2 quietly included two new UDP side channels (both reliable & best effort), which also leverage SSL (DTLS), over UDP port 3391. In the days of Windows Sever 2008 R2 and Windows 7, RDS supported the Gateway role, which uses RPC over HTTP. Here’s the quick background for you, then we’ll move in to the setup & configuration steps.
![windows server 2016 remote desktop slow windows server 2016 remote desktop slow](https://yagmoth555.files.wordpress.com/2021/01/2.png)
But did you also know that you can improve Remote Desktop performance (especially for streaming video, etc.) through this gateway simply by enabling port 3391 UDP inbound to the RDS Gateway server? No? I’m not surprised, since most people I’ve talked to just stare at me with a blank face when I mention it to them. Do you have a Remote Desktop Server ( properly) configured with the Gateway Role in your environment? In this configuration, all traffic is secured via SSL (port 443), and clients connecting over the internet to your internal RDS host(s) will be encrypted (and not necessarily identifiable as RDS traffic from the outside).