Forum Discussion
Problem adding second Load Balancer inbound NAT rule
Can someone please help me with the following issue
I have two VMs setup in Azure both with one static internal IP addresses each (10.0.0.5 and 10.0.0.6) neither of the VMs have their own public IP address.
when I built the first VM I setup a NAT rule via the load balancer no problem
when I go to add a separate NAT rule for the second VM (different port but using the same public IP address belonging to the load balancer)
e.g. Load Balancer > Inbound NAT Rules > Add
under 'associated to' is states the name of the first VM I built, therefore if I try to add a new NAT rule it only allows me to select the IP address on this first VM. I am trying to create a NAT rule associated with the second VM I built.
How do I remove this 'associated to' so I can direct a new NAT rule to the second VM
Please advise Thanks
__AUser
Correct a nat rule can only be to Single VM or availability set
3 Replies
I think I see the problem now. If I want to associate Load Balancer Inbound NAT rules to more than one VM (e.g. different ports going to different backend VMs) I have to create an Availability Set then when creating the VMs add them to the availability set as the options appear to be only
unassocaited
single VM
availability set
is that correct?
Thanks
__AUser
Correct a nat rule can only be to Single VM or availability set
- Thanks again Kent, I have it working now :)
