If you have already read the article with title: Wierd Network Interface on Windows Server 2008. I will add more information here. So this post explained more on how to troubleshoot the problem with the network interface in the previous post.
Actually that’s would not happened if I did not implement Hyper-V. After I create a virtual network interface that use external network interface, some wierd events happened, such as you can see from the pictures in the previous post.
What I did before by disabling and enabling the network interface that links to the virtual network interface used by Hyper-V may create another problem. OK, it fixed my problem with network connection, but make the connections to virtual machines become unstable, often disconnected and need to reconnect again. After some troubleshooting, I found other wierd things deal with Hyper-V.
Another problem:
I don’t know how it can happen. The MAC address of the physical network interface is the same with the MAC address of the virtual network interface created by Hyper-V Manager. I examined the problems when doing ‘ipconfig /all’.
To solve the problems with unstable connections to virtual machines, I should disable and enable the virtual network interface created by Hyper-V. In the previous picture, it was named as ‘Local Area Connection 4′. The problem may also because of the virtual network interface failed to get the IP Address automatically from the DHCP Server. Sometimes I didn’t get problems when I found that the name of physical network interface does not appear in the output of ‘ipconfig’. So I guess, the connection problems to virtual machines was actually caused by failures in having the automatic TCP/IP configuration or the ip address.
