Hyper V single Nic external network

First, let's talk about the environment: Win 8.1 single NIC (there are wireless and wired NICs, but there are no redundant network interfaces to plug in, or it is equal to a single Nic)

 

Hyper V has three vswitch types:

Private/internal/external

I don't know much about each of them, and I don't want to mislead everyone.

 

This is because CSS and JS compatibility debugging is required. ie11 is used for development. ie11 debugging tool is used to change the document mode to IE8, and jquery is found. validation cannot run normally. however, IE8 is directly used on XP installed on virtual machines, but there is no problem. It is really a headache.

 

Two computers are used for work. One is installed with Windows 7, a desktop, and a big screen. The other is a notebook win 8.1 and a small screen.

Generally, we use desktops for development. However, hyper v cannot be installed in win7. To perform compatibility debugging, we can only open a virtual machine in the notebook and then remotely connect to the virtual machine.

At the beginning, the virtual machine type was selected as an internal network, and the remote connection can only be enabled on the physical machine where the virtual machine is located. the physical machine is a small screen. It doesn't matter if you use it twice. If you use it more often, you will not be comfortable with it.

 

This afternoon, I tried to change the virtual network to an external network. The first problem is:

An error occurred while creating the vswitch. An error occurred while creating the vethernet switch. A catastrophic failure occurred during xxxxxx.

 

Without screenshots, You can't create them. I searched a lot and didn't say why.

The following command was found from the Internet:

Netsh Winsock Reset

After the command is executed, restart the instance. If no, delete all vswitches. After the command is executed, restart the instance to create an external network.

At the beginning, it was like this:

That is, the vlan id is checked.

After this check box is checked, the physical machine cannot ping the gateway and cannot connect to the network.

Display in Virtual Machine XPNetwork restricted. Manually assigned an IP address, indicating that the network is connected, but the gateway cannot be pinged, not to mention surfing the Internet.

After this check box is removed, the physical machine can ping the gateway and access the internet.

 

Please help me with it. After a long time, I still cannot.

 

Some colleagues inserted a sentence saying that the external network can only use dual NICs. I found the root network cable, but the line was too short to connect to the empty port .!! -_-

He is about to give up. Daniel said that he has installed a virtual win7 on his machine. It's okay to come up! I saw it. It's really no good!

Open the previous virtual Win8. Like XP, you cannot ping the gateway.

 

Later, I checked the Virtual Machine Configuration:

The network adapter Node also has a vlan id. When using the internal network, I hooked it up (although I don't know what it is ).

Remove this check box. In virtual XP, the network cannot be pinged, but the virtual Win8 can be pinged to the gateway.

This indicates that the problem lies in the vlan id, and the direction is correct.

Go to XP, manually assign an IP address, and then ping the gateway!

I am tossing for one afternoon...

 

The article is very poor. I just want to give a reference to the young masters who have encountered the same problem. Let's take a look.

Thank you.