This is the opposite of all the other networking issues I have seen with Hyper-V- anyone run into this?
I am running Hyper-V on a Server Core installation, and have had the same issue when I used Server 2012R2 as when I used Server 2008R2 on the same server as a virtual host. The server is an HP ProLiant DL360 Gen8 with 2x 8-core processors, 32 GB RAM. The
VM is sized and configured to stay within 1 NUMA node. It uses a single port of the 4-port HP/Broadcom 331 NIC, with all the TCP LSO settings disable at the switch, host, and guest, same with the power management settings. We have ProxyARP on the network,
so I have set the ArpRetryCount key to 0.
I have seen it happening with and without SR-IOV enabled. The guest OS is an RDS server, so for the sake of our CAL's it has to stay at Server 2008R2. I have set up a HOSTS file to mitigate this problem, as it seems to be a DNS issue- Here's what happens:
The first time I visit a resource, the server will timeout. An example not in our HOSTS file does this consistently: If I go to https://mail.mydomain.com/OutlookWebAccess, it spins for a couple of minutes before timing out. I hit refresh and the page loads
immediately. This server is colocated in-house, as is the mailserver. I'd say it is a DNS issue at some level, but I'd like to know what level it is- Is it just timing out trying to cache the DNS request, or is there a performance issue with a DNS server on
the network? (All of our DNS is AD-integrated running on DC's).
Here is where I'm seeing this:
Internet Explorer- described above
Salient Interactive Miner- at the login screen, it searches for a database and times out. If I go to the setup and enter the IP address, it still times out. It will not find the database server until I quit and restart the program. If this is the same issue,
it would obviously not be a DNS problem.
I DON'T see it in GP9 connecting to a datasource
Prior to setting up the HOSTS file, I saw this in Windows Explorer connecting to network shares on the same LAN segment.
This appears to only happen to the Hyper-V guest OS. As a best practice, whenever Windows Update runs, I update the Integration Components.
I have the bindings properly ordered on the guest VM, with the network adapter the goes to the physical NIC first, and IPv4 ordered before IPv6.
All updates are isntalled, and the firmware is at it's latest revision.
Any ideas?