At the beginning of 2025, Cloudflare announced a new solution to allow the connection via browser to Windows RDP servers not exposed over the Internet in a totally secure way. Since Windows NT4 RDP has been the way to interact with Windows servers, but it’s always been an unsecure protocol. Exposing it directly over the Internet is historically a huge risk, and the only possible solution is usually to use VPN. But VPN’s are not always easy to setup, they require a client-server component that may be blocked in hardened laptops, and they use tcp/upd ports that may be blocked by firewalls. Using a browser is a much easier solution, and Cloudflare made exactly this.
I found around many articles about this solution, but many of them were missing some fundamental steps in their how-to guides, so as I spent myself half a day to implement it for my home lab, I decided to record all the steps I’ve done.
Tag: vpn
Set a static IP in VeeamPN appliance
For a new chapter of my book on Veeam Availability Console, I created a second virtual datacenter and I needed to connect the two of them together with a vpn. I have many options, like using the embedded ipsec capabilities of the NSX Edge i have at both sites, as they both run vCloud Director, but I decided to use Veeam Powered Network, in order to use this opportunity to learn more about it. And the first thing I’ve learned was how to configure the appliance with a static IP address.
Use VeeamPN to access Cloud Connect tenants
Last week, during the VeeamON 2017 conference, one of the announcements has been a completely new product, called VeeamPN (Veeam Powered Network), a solution to easily create virtual private networks betweens multiple public clouds, remote locations and roaming users. Even if the main use case of the solution is to ease the access to Azure virtual machines, I’ve found another interesting use case that I’m sure the service providers running Veeam Cloud Connect will like.
