I installed Windows Server 2008 R2 Server Core to create a Hyper-V server for a test environment. After finalizing the settings and configuring the firewall, I established a remote connection to the Hyper-V server.
My first step was to create two virtual switches, one “Internal Network” and an “External Network”. The external connection is linked to the physical network card on the server. After applying the “External Network” I lost the connection with the server. I forgot that Hyper-V disables all network bindings except the “Microsoft Virtual Network Switch Protocol”. I Googled to find a way to enable the protocols and found “nvspbind.exe” that can be downloaded here. With NVSPbind you can reset, disable/enable the network bindings and change the NIC order. It is a very useful tool that can save a lot of time.
To get the name and GUID I used a Powershell script because it gives a better overview.
Get-WmiObject -Namespace "rootcimv2" -Query "select * from Win32_NetworkAdapter WHERE PhysicalAdapter = 'True'" | Select-Object NetConnectionID, GUID
NOTE: I run the NVSPbind from a Powershell prompt. To run in a CMD prompt remove the &.
I checked the enabled and disabled network bindings with the following command.
& NVSPbind "Local Area Connection"
I want to enable all network bindings except IPv6. To accomplish that, I enable the network bindings individual.
& NVSPbind /e "Local Area Connection" ms_netbios & NVSPbind /e "Local Area Connection" ms_server & NVSPbind /e "Local Area Connection" ms_msclient & NVSPbind /e "Local Area Connection" ms_tcpip & NVSPbind /e "Local Area Connection" ms_lltdio & NVSPbind /e "Local Area Connection" ms_rspndr
After running the commands I had my network connection back and was able to remotely access the server.