SERVER 2016 REMOTE DESKTOP ERROR 23003 WINDOWS

The reason is that it uses two HTTP channels (one for input and one for output) and DNS round robin cannot guarantee that both these connections will be routed trough the same RD Gateways server which is a requirement for it to work.

SERVER 2016 REMOTE DESKTOP ERROR 23003 WINDOWS

In regards to RD Gateway in Windows Server 2012 (R2), you can no longer use DNS Round Robin for load balancing with the new HTTP transport. I have done 2 when it was good enough or the only option but I have never liked 3, bar where itРІР‚в„ўs all whatРІР‚в„ўs needed, because it just doesnРІР‚в„ўt fit many of the uses cases I dealt with. I prefer the first but all 3 will do the basic job of load balancing the end-user connections based on the traffic.

DonРІР‚в„ўt get me wrong for some use cases itРІР‚в„ўs fine, but for many it isnРІР‚в„ўt. That sort of works but has the usual drawbacks for problem detection and failover. ItРІР‚в„ўs in no way an РІР‚СљApplication Delivery ControllerРІР‚Сњ as load balancer are positioned nowadays. It works but itРІР‚в„ўs rather limited in regards to intelligence for failure detection & failover. Each has itРІР‚в„ўs use cases with benefits and drawback but you have many options for the many situations you might encounter. These support layer 4, layer 7, geo load balancing etc. KEMP has Hyper-V appliances, many others donРІР‚в„ўt. Load balancing appliances (KEMP Loadmaster for example, F5, A10, РІР‚В¦) or Application Delivery Controllers, which can be hardware, OEM servers, virtual and even cloud based (see Load Balancing In An Ever More Demanding Virtualized & Cloudy World).When in comes to the actual load balancing of the connections there are some changes in respect load balancing from Windows Server 2008 R2 that you need to de aware of! With Windows 2008 R2 you could do: On the RD Gateway side you have capability of configuring a farm with multiple RD Gateway servers.

When you need to make the RD Gateway service highly available you have some options.

Server 2016 remote desktop error 23003