Hello,
We have two Hyper-V Server 2019 Core servers. One has been around awhile. It runs on an old PC repurposed as sort of Test system. The other Hyper-V server runs on brand new Dell T440 Server. For the most part, both servers run fine, but I am having an unusual problem with the new Dell server.
When I open Server Manager on my desktop PC, the older Hyper-V server populates in Server Manager right away. The Dell server takes a few minutes before it appears in the list of servers. If I open Hyper-V manager from my desktop, the older server populates right away and I can immediately connect to VMs, manage settings, etc. On the other hand, the Dell server takes a few minutes before it even appears in the list of servers. Then, when I select the Dell server, it again takes a minute or two before the two VMs running on it appear in the Hyper-V Manager. When I try to connect to one of the VMs, again, it takes a minute or two before the Virtual Machine Connection window appears, and then it sits there "not responding" for another minute or two before the VM's login screen appears. However, once I am connected, everything moves along without delays. Furthermore, in Hyper-V Manager, if I try to change any settings, etc., for the Dell server, it takes a while for anything to happen. With the older server, I have no such problems.
Both servers and my desktop are connected to the same switch, in a small office network. There is nothing terribly complicated about the network here. I tried running Wireshark, just to see what was happening. I see constant traffic going back and forth between my desktop and the Dell Hyper-V server while I'm waiting for the information to fill in in Server Manager, or in Hyper-V Manager, or while waiting for Virtual Machine Connection window to respond. So, at least I know it's not like there is no network connectivity, or anything like that.
I've tried using different ports on the switches, different Ethernet cables, etc. I've tried updating the Ethernet drivers, Dell server firmware, installing Microsoft Updates, etc. Nothing seems to help.
Can anyone suggest a possible solution to the problem? Or point me in the direction of finding a solution?
Thanks,
Rick