September 11th, 2013, 02:35 AM
Windows server virtual machine (UTM) networking
I'm having some trouble with my current network set up. Connectivity randomly drops for a moment every now and then, and sometimes completely until I restart the server. Pinging the server times out.
Setup: Windows server 2012 with Sophos UTM 9.1 (built on Linux) running in Hyper-V. I'm using one nic for the virtual switch. There are two virtual adapter for the UTM virtual machine. One for internet connectivity (IP:10.0.0.3) and one for communication between Windows server and the virtual UTM (192.168.1.3). Internet is served by the router (10.0.0.2 - DHCP turned off) The virtual adapter that was created in windows is 192.168.1.1.
I'm using DHCP to assign IP's to the client PC's (192.168.1.101-192.168.1.200)
I've tried changing the set up by connecting the server to the internal network using an unused NIC and using the second nic for the virtual switch, and then bridging the virtual adapter created inside windows with the NIC connected to the internal network. That caused even more connection problems (losing connection with shared folders, but not necessarily with server)
In Hyper-V manager on the networking tab under status it says "Degraded (integration services upgrade required)" Should I change the network adapters to legacy? To me it doesn't make sense that the virtual adapter created in the virtual machine would be the problem. If they were, wouldn't I only lose connectivity to the virtual machine instead of the whole server?
September 18th, 2013, 02:07 PM
Is the connection issue outside of the Host also or just isolated to the Hyper-V host?
My first guess would be a bad configuration..
Hyper-v is a pain when dealing with multiple nics. Are you using ipv6 at all or do you have it disabled? I have seen this cause issues when running virtual switching.
I do like Hyper-v but if you plan on running non windows VM's I would suggest using Vmware or even Xen Server as they both have free versions and normally support most appliances.