The organisation I work for is trying to move away from hosting our own VMs and move them all into the cloud, namely into Azure. Its all new to us, and so the first item I'm trying to tackle is setting up a VM which hosts the license server for an automation application we use.
Creating a Windows VM in the Azure resource manager was easy. And with the license server installed on that VM, I find that it can serve licenses to the automation application instances on the other Azure VMs I've created.
The problem though:
We can only have one license server current, so this license server in the cloud, still needs to service the automation applications we run on our local machines.
The license server just needs the TCP/UDP port 7266 open, so I've made sure that port is open on the Windows instance, as well as gone into the Azure NSG to ensure that an inbound and outbound rules have been added to allow that port.
My understanding is that for the new Azure VMs in the resource manager (i.e. not classic) don't need endpoints. I've added the public IP in Azure with a DNS name, and that resolves from our network to match the public IP of the targeted Azure VM.
But regardless of whether I use the DNS or the specific IP address, our machines consistently get:
ERROR: No connection could be made because the target machine actively refused it [::ffff:220.127.116.11]:7266
I'm hoping someone is familiar enough to assist me in how to configure an Azure VM to make a service publicly accessible from outside Azure.
The Azure forums haven't offered any new options for me to try other that the inbound rules. I'm guessing i'm missing something simple?