What If the Hop Count of a Cloud Desktop Is Abnormal?

Scenarios

After the network of a cloud desktop is reset, the hop count is restored to the default value, which may cause Internet access failure.

Procedure

1. Press Win + R on the desktop. In the Run dialog box, enter cmd and press Enter to open the CLI.
2. Enter route print and press Enter to view the result.
   

   The service NIC is the subnet NIC in the VPC created by the user.

   • Normal routing

     Example: There are two routes. The hop count of the service subnet is 4. A value smaller than 5 indicates that the service NIC has a high priority and the routing is normal.

     

   • Abnormal routing

     Example: There are two routes. The hop count of the service subnet is 7. A value greater than 5 indicates that the service NIC has a low priority and the routing is abnormal.

     

   • Abnormal routing

     Example: There are two routes. The hop count of the service subnet is 5, indicating that the service NIC is the same as the NIC of the management CIDR block. As a result, network requests cannot distinguish the NICs and the routing is abnormal.

     

3. Press Win + R on the desktop. In the Run dialog box, enter ncpa.cpl and press Enter to go to the Network Connections page.

   

   

   Depending on the desktop system version, you may find multiple NICs or only one NIC.

4. Double-click the service NIC. In the displayed dialog box, click Properties. On the Networking tab, double-click Internet Protocol Version 4 (TCP/IPv4) to go to the Internet Protocol Version 4 (TCP/IPv4) Properties page.
5. Click Advanced. On the IP Settings tab, deselect Automatic metric and set Interface metric of the service NIC to a value less than that of the management CIDR block. For example, if the hop count of the management CIDR block is 5, the value of Interface metric of the service NIC must be less than 5.

   

6. Click OK.