What do I do if a general fault occurs when I ping the public IP address of a Windows instance? -

Identify and resolve causes of "general fault" or "common issue" errors when pinging the public IP address of a Windows ECS instance.

Problem description

When you ping the public IP address of a Windows instance, the system returns a "general fault" or "common issue" error.

Causes

This issue can have multiple causes. The following table lists possible causes and solutions.

Cause	Solution
Third-party antivirus or security software is installed on the instance.	Check third-party antivirus or security software
The gateway or route configuration of the instance is incorrect.	Check the gateway and route configuration
Other causes	Other causes

Solutions

Check third-party antivirus or security software

Third-party antivirus or security software may control network traffic like a firewall.

Uninstall or temporarily disable the software, then ping the public IP address again.

Check the gateway and route configuration

An instance requires a correct default gateway and default route to access the Internet. If either is missing or incorrect, perform the following steps:

Step 1: Check the default gateway configuration

Run ipconfig to view the default gateway configuration.

Verify the default gateway address against the IPv4 CIDR block of the vSwitch to which the instance is connected. The correct default gateway address is the third-to-last address within the CIDR block. In this example, the vSwitch CIDR block is 172.16.0.0/24, so the correct default gateway address is 172.16.0.253.

If no default gateway is displayed or the address is incorrect, reconfigure it as follows.

Configure the default gateway

Note

This example uses Windows Server 2022.

Open Network and Sharing Center.
Click Change adapter settings.
Double-click the primary ENI named Ethernet, then click Type in the Ethernet Status dialog box.
In the Ethernet Properties dialog box, double-click Internet Protocol Version 4 (TCP/IPv4).
In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, select Obtain an IP address automatically for automatic assignment, or select Use the following IP address to manually configure the IP address and default gateway.
Click OK.

Step 2: Check the default route

Run route print to check whether a default route exists.

The route with network destination and network mask both set to 0.0.0.0 is the default route. The instance uses the default route to access the Internet.

If no default route exists, add one. Replace <Default gateway address> with the actual gateway address:

route -p add 0.0.0.0 mask 0.0.0.0 <Default gateway address>

Example:

route -p add 0.0.0.0 mask 0.0.0.0 172.16.0.253

Other causes

The following factors may also cause this issue:

A network adapter is disabled or malfunctioning.
The network protocol stack is damaged due to viruses or malware.
Built-in network tools (disabled by default) are enabled but misconfigured. Temporarily disable these tools and configure rules to restrict traffic for troubleshooting.

Check the status of the network adapters

Open Device Manager.
Check whether the network adapters work as expected. Enable any disabled adapter. If an adapter is malfunctioning or outdated, update the driver. See Install the Alibaba Cloud virtio driver.

Reset the TCP/IP stack

If the TCP/IP stack is damaged, such as due to registry corruption, reset it:

netsh int ip reset
netsh winsock reset

After the reset, repeat the Check the gateway and route configuration step.

Check the system firewall

In this example, Windows Server 2012 is used. Steps for other Windows Server versions are similar.

In the lower-left corner of the desktop, click the icon to open Server Manager.
In the upper-right corner, choose Tools > Windows Defender Firewall with Advanced Security.
Check the firewall status.
1. If the firewall is disabled, no action is required.
2. If the firewall is enabled:
  1. In the Windows Defender Firewall with Advanced Security window, click Outbound Rules.
  2. Check whether any block rule prohibits outbound access. If so, disable or modify the rule.

Check local security policies

Open Local Security Policy.
Click IP Security Policies On Local Computer, right-click an existing policy, and select Type. Review the policy settings.
If Yes is displayed in the Policy Assigned column and the policy contains block rules, disable or modify the policy.

Check the routing and remote access tool

Open Server Manager. In the upper-right corner, choose Tools > Routing and Remote Access.

Note
If the Routing and Remote Access tool is not found, it is not installed and no action is required.
Disable the tool.