Record the provider network requirements

Get the address allocation, gateway information and any routing requirements from the server provider. Keep host management access separate in your plan from the addresses assigned to customer virtual machines. Guessing the network model can leave both the host and guests unreachable.

Distinguish NAT from routed addresses

A NAT arrangement and a deployment using routed public IPs need different configuration. Identify which model your provider supports before setting up IP pools. Check how customers will receive inbound traffic and whether any port mapping is required.

Test one guest first

Provision a test virtual machine and check its configured address, outbound connection and intended inbound access. Review the host, guest and provider firewalls separately. A firewall rule in one location does not describe the entire path.

Keep a recovery route

Arrange working console access before changing the host network. A Virtualizor license supplies a management component, not an address allocation. Use LicenseCage instructions for activation and the relevant provider guidance for your network.

A practical example

A host can reach the internet while a newly created guest remains unreachable. That result does not identify a licensing problem: the guest may have an incorrect address or gateway, the provider may route addresses differently from your template, or filtering may occur outside the host. Trace one guest from its own interface through the host and provider network before changing multiple settings.

Checks to make

  • Record the provider's assigned address block, gateway and permitted network model.
  • Confirm whether the guest needs a public routed address or an explicitly designed NAT mapping.
  • Check guest, host and provider firewall rules separately for the required service.
  • Test outbound connectivity and a deliberate inbound connection from another network.

Making the decision

Keep working console access throughout the investigation. Make one reversible change at a time and document the result. A reproducible test on one guest gives a safer basis for provisioning customers than applying speculative network changes across the host.