Deploying 3CX on Hyper V

[rjamesm2884]

Hello,

We are in the process of moving our 3CX server in Azure to a Hyper V VM that is also in Azure. We installed 3CX on the VM but we can't figure a way to share the virtual connection without deploying a NAT within the Hyper V environment this causes a huge problem when enabling DHCP and Routing and Remote Access since you have to forward a ton a ports and it's not practical to do it one by one. Anyone has done this before?

This is our layout in Azure

Sophos XG Firewall => Port A (Public IP), Port B (Internal IP) => All ports configured in the Firewall => Windows 2019 Data Center => Hyper V VM (3CX) => Virtual Network (External Switch doesn't pass through Internet so you need to create an Internal network switch with DHCP and Routing) => The issues begin here Port Forwarding becomes a mess.

What I would like is the Firewall to provide DHCP to all VM's in Hyper V so we can specify what private IP has access to what ports from the Firewall.

 

[cobaltit]

I'm confused. What is stopping you from making a VNET with internet access?

 

[rjamesm2884]

That's how is set up right now. We have a VM deployed with Debian on Azure works fine with it's own VNET. We are trying to consolidate servers and put them behind a firewall VM box in azure. Goal is to reduce cloud server cost. The environment we are trying to set is called a Nested Hyper V but it doesn't seem possible to use a DHCP server with Routing to access through 3CX.