<div>
There it was, right there in the logs....port 5504 needed to be open.
</div>


There it was, right there in the logs....port 5504 needed to be open.

<div>
<div class="content wysiwyg-content">
We have a brand new RDS environment on Server 2016. &nbsp;It was set up by Microsoft who came onsite to help us. &nbsp;It worked great.<br />
<br />
THEN - some genius IT director decided our gateway servers need to be in a DMZ. &nbsp;<br />
<br />
Now, it doesn't work and I need help finding out why.<br />
<br />
What ports are needed from the gateway server to the Connection broker? &nbsp;I currently have 443 and 3389 open from the gateway servers to the connection brokers.<br />
<br />
The gateway servers are pointed to a load balanced VIP in front of our two connection brokers.<br />
<br />
My network guy tells me it's all configured correctly, but the only thing that changed was that the two gateway servers moved to a DMZ. &nbsp;Nothing in the config of the deployment changed.<br />
<br />
Anyway, how do I go about troubleshooting this please?<br />
<br />
Thanks<br />
<br />
Cliff
</div>
</div>


We have a brand new RDS environment on Server 2016.  It was set up by Microsoft who came onsite to help us.  It worked great.

THEN - some genius IT director decided our gateway servers need to be in a DMZ.  

Now, it doesn't work and I need help finding out why.

What ports are needed from the gateway server to the Connection broker?  I currently have 443 and 3389 open from the gateway servers to the connection brokers.

The gateway servers are pointed to a load balanced VIP in front of our two connection brokers.

My network guy tells me it's all configured correctly, but the only thing that changed was that the two gateway servers moved to a DMZ.  Nothing in the config of the deployment changed.

Anyway, how do I go about troubleshooting this please?

Thanks

Cliff

RDS - Server 2016 and how to test where it's broken

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.