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

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.