Comments on: Azure Load Balancer For RDP

By: Pixel Robots.

Pixel Robots. — Fri, 30 Apr 2021 11:28:20 +0000

Hey, this blog post was created way back in 2017. Azure bastion was not a thing then. But you are right go with Bastion if you can.

By: Dhawal Baranwal

Dhawal Baranwal — Fri, 23 Apr 2021 07:43:01 +0000

Just curious to know what can is the need of such scenario, If we have to just RDP to the VMs can’t we use bastion service ? which is more reliable and secure?

By: Dude

Dude — Sun, 20 Oct 2019 06:09:13 +0000

Why would I not use a load balancing rule with a public FE-IP that listens to RDP-338p and fwds is to 3389 on a specific VM (backend pool)

Trying to understand the difference in using the NAT to translate publc ip 3389 to private ip 3389, vs using a Load balancer rule.

Initially I thought the rule will only work with fe-pub to BE-pub and not FE-pub to BE-private.. but it can work like that by accepting the rule in the config with public to private.

By: Rob Burns

Rob Burns — Tue, 30 Jul 2019 12:57:29 +0000

I agree with Lee Gratton that the load balancer should be able to load balance between multiple backend VM’s using a connection to the public IP and a single port#. You should not need to use other port numbers, unless you specifically need to connect to a specific backend server for maintenance etc. The reason I believe this is the case is that the Microsoft examples of load balancing in Azure use web traffic as the application- you can go to a single public IP on port 80, and the traffic is balanced across multiple backend servers. If it works for port 80, why not for RDP?

By: Pixel Robots.

Pixel Robots. — Sat, 10 Mar 2018 12:26:57 +0000

In reply to Lee Gratton.

Hello,

The use of the Load Balancer is to use one IP address (the Load Balancer) instead of one IP address per VM. The way the Load Balancer works you need to map one port to per VM. So, in essence, you can connect to multiple VM’s via one IP address, you just need to change the port of the VM you like.

I hope that makes more sense. Please reply if you need any more help.

Thanks

Pixel Robots.

By: Lee Gratton

Lee Gratton — Sat, 10 Mar 2018 12:13:05 +0000

I’m confused by this. When creating the LB and then creating the NAT rules, you are specifying particular ports per VM. So when connecting to the LB via RDP, and specifying the port, you are still only connecting to that one VM. Surely the purpose of the LB is to select either VM via the LB IP address?

By: Pixel Robots.

Pixel Robots. — Wed, 28 Feb 2018 20:03:57 +0000

In reply to Pavan Muppidi. If you send me an email with a screenshot of your load balancer setup I will happily help you.

By: Pavan Muppidi

Pavan Muppidi — Wed, 28 Feb 2018 01:09:25 +0000

I’m able to connect to VM1. (PublicIP:VM1Port)
I am unable to connect to VM2. (PublicIP:VM2Port).
If I stop the VM1 the public IP is not available.
Please advise.
Note: Able to RDP VM2 with its direct IP from VM1.

By: Pixel Robots.

Pixel Robots. — Tue, 05 Dec 2017 16:50:26 +0000

In reply to Sundaram Ramakrishnan. How have you set your inbound ports on the NSG? Feel free to email me for further help.

By: Sundaram Ramakrishnan

Sundaram Ramakrishnan — Tue, 05 Dec 2017 16:08:25 +0000

Thanks for this helpful article. My scenario is, my VMs are within a Virtual Network and Load Balancer. I have white listed my machine’s IP in the Nework Security Group. But still I’m not able to RDP my VMs from my machine, by FOLLOWING THE ABOVE STEPS. Please help