rseiler

It might very well have resolved it, but I was still unclear on the particulars. I found a workaround, however: set the Hyper-V Network Management Service on delayed automatic start (in the properties of the service). That allows enough time for the network to start before Hyper-V jumps in and tries to use it.

My thought in having two NICs was for RDS: NIC1 handles the RDS traffic, while NIC2 handles backchannel communication between the RDS server and our domain server (transferring files that people open, etc). I'm just trying to distribute the load a bit, and the traffic accumulation on each (light for NIC1, heavy for NIC2) bears that out. There's only one subnet, so I don't think adding a route is appropriate, right? NIC1 has the gateway configured, NIC2 does not. I looked at the bindings and see that right now the internal-only virtual network I setup for HyperV is first (it didn't even exist initially--I just added it today), NIC2 is second, and NIC1 is last. Armed with that information, what do you suggest? Thanks

Funny, since I'm looking at the same issue today. Do you have one NIC or two? We have two, and the second one purposefully doesn't have a gateway (there's a warning when you try to enter one), so I wonder if that's the issue. If there's only one NIC, I can certainly see how that would be the problem--though you'd have more noticeable problems than this, I think.