We have dozens of tentacles installed on various instances of Windows server, but there’s one I’m struggling to get working.
I have an Azure VM installed using the ‘new’ Resource Model. Tentacle 2.6 is installed, and listening on port 10933. The tentacle added a firewall rule to the Windows Firewall. The VM has an azure network interface using an azure Network Security Group, and I’ve added a rule for Ocopus Deply: Source Any, Destination Any, Service Custom (TCP/10933), Allow.
No matter what I do I cannot connect to the tentacle on port 10933.
But, if I follow the exact same procedure, but configure the tentacle to listen on port 8080, add a windows firewall rule for port 8080, and an Azure NSG rule for port 8080 it works??
I guess this is more of an Azure question, but has anyone else seen this kind of behaviour on a Azure Resource model VM?