UTM HOME EDITION INSTALL ISSUE NOT WORKING AS IT SHOULD ON VMWARE WORKSTATION

Hi, and welcome to the UTM Community!

Please edit your post to change it into sentence case instead of all uppercase.

Cheers - Bob

I  have responded on the post Bob ,

Thank you

Which version of VMWare are you using? If you are using VMWare Workstation I'd recommend you read the user's manual as it's pretty detailed in setting up network connections.

Hello Kamran,

I want to help, but I do not understand your configuration either. A detailed description of your hardware and network configuration would help us understand better. 

I have a Sophos UTM running under VMware Fusion (Mac). I described its setup here:

https://community.sophos.com/products/unified-threat-management/f/52/p/27167/80436#80436

Even though it seems confusing and there are many Mac-specific instructions, VMware Fusion and VMware Workstation are very similar products, and you should be able to make it work for you. See the section called "Configuring VMware Virtual Machine". It may help a little.

Here is my home hardware configuration:

Internet <-> (cable) Cable Modem (ethernet) <-> Ethernet / USB 3 Adapter (External WAN, DHCP, IPv4/IPv6) <-> Mac mini (UTM in virtual machine) <-> Built-in Ethernet (LAN, private network, e.g. 10.x.x.x or 192.168.x.x) <-> Ethernet switch for home network

Here are a few VMware hints that may help you:

• I created a new virtual machine from the .iso file, but then I chose "Custom Configuration" so I could changed the settings and edit the .vmx file first before starting the .iso installer. 
• The virtual machine has two Ethernet adapters. You will have to add one. Both Ethernet adapters are set to Bridged mode in VMware.
• Sophos recommends that you edit your .vmx file in your virtual machine to change the network adapter drivers from "e1000" to "vmxnet3". There will be two entries in the file, one for each network adapter.
• For Operating System, choose Linux -> Suse Linux Enterprise 11, 64-bit.
• Choose the number of cores for your virtual machine carefully. You cannot change the number of cores after you install the UTM in your virtual machine. I have a quad (4) Core i7 in my Mac. I gave my UTM two cores in VMware. Do not give your virtual machine more than total hardware cores - 1. Hyperthread cores do not count.
• I chose 8192 MB for my UTM in VMware. My Mac has 16 GB of RAM installed. You can change the memory for your virtual machine memory at any time. Just shutdown the UTM first, then change the memory setting in VMware.

When you are ready, boot the VMware virtual machine. Follow the prompts during installation.

Tell us more about your system and network, and we may be able to help more. Good luck!

hi utmadm,

Thank you for your time. I still can't get UTM to work.

I posted a network Diagram with how I am trying to do this. I have turned off all firewall. I still can't understand why it doesn't work, I get no internet access on the end machine from the core switch. and Can't see any activity on the WAN. I'm very confused to how this program works. 

My understanding is with the Physical Firewall I have installed in the past. that you take the cable from the router/modem plug this in to the WAN and the LAN to the Switch. Not sure because this is a VM i'm messing this up but please do help i feel helpless. 

My Hardware Dell T110 II Power Edge Server with Three NIC''s Two are qlogic bcm5709c and 1 broad com. I have 32 gb ram and VM Workstation installed on this machine. The host os is W10 Pro. The VM's i have on here are UTM and Window Server 2012 R2. Vmware has three Virtual Networks Configured. VMXNET0, VMXNET1, VMXNET2.
VMXNET0 is the WAN which is Bridged to the qlogic bcm5709c NIC 1 46. VMXNET1 is the LAN which is Bridged to the qlogic bcm5709c NIC 2 47. Where the UTM Internal is assigned.  this is plugged in the core switch. VMXNET2 is the NIC for the Window SVR 2012 R2 which is coming from the core switch.

I noticed when the Virgin Router is in Modem Mode UTM won't pick up any info under Ethernet DHCP. however my host machine is picking the information with the IP address. Like wise evan when i Put the Virgin Router in Router Mode with DHCP. It does than pick up an address but can't see any traffic on the WAN. And any device Connected to the Core switch won't get any internet.. My main issue is that i can't get WAN to work ! thought LAN show's activity . How do i do this setup! I have tried your instruction for( Change the network adapter drivers from "e1000" to "vmxnet3") . I have also setup the Masquerading rule, and firewall rule as per Sophos Instruction.

Any one who uses VMworkstation and Virgin Router / Modem can they please advice on how I should setup this.

Based on the information you gave, is this a business installation?

Nope this is a home lab Environment

Is anyone able to Skype to discuss this, I just want to know how I should be going about setting the UTM up. with the descripted hardware and setup.

Am I the only one who is struggling to understand the network diagram that Kamran posted? What I think I am seeing is:

Internet <-> Virgin Super Hub (Internet bridge) <-> UTM External WAN on Phys Nic 1 <-> UTM <-> UTM Internal LAN on Phys Nic 2 <-> LAN on Core Switch

and ...

Other virtual machines running on the Host Server <-> Phys Nic 3 <-> LAN on Core Switch

There are three physical devices, right? :

1. Virgin Super Hub 2 - this is the bridge to the Internet

2. Host Server - This has three physical NICs (ethernet adapter)

a. Physical NIC 1 - This is connected to the Virgin Super Hub 2 and through it to the Internet. It serves as the WAN (External) connection to the Internet for the UTM

b. Physical NIC 2 - This is connected to the Core Switch and serves as the LAN (Internal) connection for the UTM. 

c. Physical NIC 3 - This is also connected to the Core Switch and serves as the LAN connections for additional (not the UTM) virtual machines running on the Host Server. 

3. Core Switch - This is a typical Ethernet switch for other physical computers that might be running on the LAN behind the UTM.

There are only two networks involved, right?:  One WAN (to the Internet) and one internal private LAN behind the UTM, right? All internal devices - the Host Server, virtual machines, Core Switch, and any additional devices attached to Core Switch - all of them are on the same internal LAN, right?

If the above assumptions are true, then I wonder why there is a need for (2c) Physical NIC 3? Furthermore, if there are no other physical devices attached to the Core Switch (e.g., other computers on the LAN), then there should be no need for the Core Switch, either.

In my UTM virtual machine setup, the UTM and the "Host Server" (a Mac mini) share the built-in Ethernet adapter and are on the same private LAN (10.x.x.x /24). If I were running additional virtual machines on my Host Server, I would put them in bridged networking on the built-in Ethernet on the same private LAN, too. I will text it out when I have time to see that it works.

My Host Server (Mac mini) is configured so that its built-in Ethernet has a dedicated IP address on the private internal LAN (10.x.x.x), which is provided by the virtual UTM. My Host Server is configured so that the additional Ethernet adapter (USB-Ethernet) has no IPv4 address (IPv4 disabled) and a Link-Local IPv6 address. In other words, the Host Server itself cannot communicate directly over the USB-Ethernet adapter to the Internet. It must use its built-in Ethernet to communicate to the Internet over the 10.x.x.x network through its own UTM virtual machine. It shares that same built-in Ethernet with the LAN side of the UTM (VMware bridged networking). 

As promised above, I ran a quick test this morning. I installed a new Ubuntu MATE virtual machine on my Mac mini Server (Host Server) with bridged networking on the built-in Ethernet interface. As expected, the new virtual machine got an IP address from the Sophos UTM DHCP server on the internal 10.x.x.x network and routed its Internet communications through the virtual machine UTM for updates, etc.

Everything worked perfectly. The new Ubuntu virtual machine and the Sophos UTM virtual machine ran on the same host server without problems or interference. At the same time, the Host Server (Mac mini) does its own server work on the LAN also behind the virtual machine UTM. For example, the Host Server ran a network backup operation for my desktop computer over the LAN. The backup occurred concurrently with the Ubuntu MATE installation and configuration. 

As promised above, I ran a quick test this morning. I installed a new Ubuntu MATE virtual machine on my Mac mini Server (Host Server) with bridged networking on the built-in Ethernet interface. As expected, the new virtual machine got an IP address from the Sophos UTM DHCP server on the internal 10.x.x.x network and routed its Internet communications through the virtual machine UTM for updates, etc.

Everything worked perfectly. The new Ubuntu virtual machine and the Sophos UTM virtual machine ran on the same host server without problems or interference. At the same time, the Host Server (Mac mini) does its own server work on the LAN also behind the virtual machine UTM. For example, the Host Server ran a network backup operation for my desktop computer over the LAN. The backup occurred concurrently with the Ubuntu MATE installation and configuration.