What do I do if network interfaces are missing from a Window instance? - Elastic Compute Service

This topic describes the cause of the following issue and how to resolve the issue: After you log on to a Windows Elastic Compute Service (ECS) instance by using Virtual Network Computing (VNC), you cannot find network interfaces on the instance.

Problem description

After you connect to a Windows instance by using VNC, you cannot find network interfaces in the Network Connections window but can find installed network interface drivers in the Device Manager window. After you run the ipconfig command on the instance, the command output contains the information about network interfaces.

Solution

Connect to the Windows instance.
For more information, see Connect to a Windows instance by using a password.
Run the following command to obtain the names, IPv4 addresses, and subnet masks of the missing network interfaces:
```
ipconfig
```
Run the following command to add the missing network interfaces:
```
netsh interface ip set address name="<$Name>" source=static addr=<$IP> mask=<$Mask>
```
Note
- Set <$Name> to the name of a missing network interface that you obtained from the ipconfig command output.
- Set <$IP> to the IPv4 address of a missing network interface that you obtained from the ipconfig command output.
- Set <$Mask> the subnet mask of a missing network interface that you obtained from the ipconfig command output.