Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ NAT Gateway/ FAQs/ Public NAT Gateways/ What Can I Do If Connection Between My Servers and the Internet Fails After I Add SNAT and DNAT Rules?

What Can I Do If Connection Between My Servers and the Internet Fails After I Add SNAT and DNAT Rules?

Updated on 2025-01-02 GMT+08:00

Symptom

You have bought a public NAT gateway and added SNAT and DNAT rules, but your servers cannot access the Internet or provide services accessible from the Internet. Whether the network configured with a public NAT gateway can connect to the Internet depends on the route table configuration, security group configuration, and network ACL configuration. If any configuration problem occurs, the network connection will fail. This section describes the fault locating process after a public NAT gateway is configured.

Fault Locating

The following fault causes are listed in descending order of occurrence probability.

If the fault persists after one possible cause is ruled out, move down the list to the other possible causes.

Figure 1 Network disconnection troubleshooting
Table 1 Network disconnection troubleshooting

Possible Cause

Solution

The route table is incorrectly configured.

Add the default route or a route pointing to the public NAT gateway to the route table. For details, see Checking Whether Default Route Pointing to the Public NAT Gateway Is Configured in the Route Table.

The ECS has an EIP bound.

Unbind the EIP from the ECS. For details, see Checking Whether the ECS Has an EIP Bound.

The security group rules are incorrectly configured.

Configure ECS security group rules to allow traffic to and from the ECS. For details, see Checking Whether Security Group Rules Allow Traffic to and from the ECS Port.

The network ACL is incorrectly configured.

Add network ACL rules to allow traffic in and out of the subnet. For details, see Checking Whether Network ACL Rules Allow Traffic in and out of the Subnet.

The EIP bandwidth exceeds the threshold.

Increase the EIP bandwidth by referring to Checking Whether the EIP Bandwidth Limit Has Been Exceeded.

The service volume of the Public NAT gateway exceeds the upper limit.

Increase the public NAT gateway specifications. For details, see Checking Whether the SNAT Connection Limit for the Public NAT Gateway Has Been Exceeded.

The buy status is abnormal.

Ensure that the public NAT gateway is running. For details, see Check Whether the Public NAT Gateway Status is Normal.

The ECS port is not listened on.

Enable the ECS port again. For details, see Checking ECS Ports.

Checking Whether Default Route Pointing to the Public NAT Gateway Is Configured in the Route Table

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Click Service List in the upper left corner. Under Networking, select Virtual Private Cloud.
  4. In the navigation pane on the left, choose Route Tables.
  5. In the route table list, click the name of the route table associated with the VPC to which the public NAT gateway belongs.
  6. Check whether default route (0.0.0.0/0) pointing to the public NAT gateway is in the route list.
    • If no, add the default route pointing to the public NAT gateway to the route table.
      1. Click Add Route and configure required parameters.
        Figure 2 Add Route
        Table 2 Descriptions of route parameters

        Parameter

        Description

        Destination

        The destination CIDR block

        Set it to 0.0.0.0/0.

        Next Hop Type

        Set it to NAT gateway.

        Next Hop

        Set it to the ID of the public NAT gateway you purchased.

        Description

        (Optional) Supplementary information about the route

        Enter up to 255 characters. Angle brackets (<>) are not allowed.

      2. Click OK.
    • If a default route is there but does not point to the public NAT gateway, add a route pointing to the public NAT gateway to the existing route table. Alternatively, create a route table and add a default route pointing to the public NAT gateway to the new route table.
      • To add a route pointing to the public NAT gateway to the existing route table, perform the following steps:
        1. Click Add Route and configure required parameters.
          Figure 3 Add Route
          Table 3 Descriptions of route parameters

          Parameter

          Description

          Destination

          The destination CIDR block

          Next Hop Type

          Set it to NAT gateway.

          Next Hop

          Set it to the ID of the public NAT gateway you purchased.

          Description

          (Optional) Supplementary information about the route

          Enter up to 255 characters. Angle brackets (<>) are not allowed.

        2. Click OK.
      • Create a route table and add a default route pointing to the public NAT gateway.
        NOTE:

        To create a route table, click Increase Quota in the Create Route Table dialog box or choose Service Tickets > Create Service Ticket in the upper right corner of the Route Tables page to increase your route table quota first. For more information, see Creating a Service Ticket.

        1. In the upper right corner of the Route Tables page, click Create Route Table and configure required parameters.
          Table 4 Descriptions of route table parameters

          Parameter

          Description

          Example Value

          Name

          (Mandatory) The name of the route table

          Enter up to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed. Spaces are not allowed.

          rtb-001

          VPC

          (Mandatory) The VPC that the route table belongs to

          vpc-001

          Description

          (Optional) Supplementary information about the route table

          Enter up to 255 characters. Angle brackets (<>) are not allowed.

          N/A

          Route Settings

          Information about routes

          You can click Add Route to add more routes.

          Set Destination to 0.0.0.0/0, Next Hop Type to NAT gateway, and Next Hop to the public NAT gateway you purchased.

          N/A

        2. Click OK.

          An Information dialog box is displayed, indicating that you can associate the route table with a subnet now or later.

        3. Click Associate Subnet.

          The Associated Subnets tab is displayed.

        4. Click Associate Subnet and select the subnet to be associated.
        5. Click OK.

Checking Whether the ECS Has an EIP Bound

If both SNAT and EIP are configured for an ECS, the EIP is preferentially used for data forwarding.

If both DNAT and EIP are configured for an ECS, the ECS will have two EIPs, one that is bound to the ECS and one that is associated with the DNAT rule. Incoming data will be forwarded by one of the two EIPs, which is determined by the user of the client. Outgoing data will be forwarded by the EIP bound to the ECS in priority. If the two EIPs are different, data forwarding will fail.

If the ECS has an EIP bound, perform the following steps to unbind the EIP.

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Elastic Cloud Server.
  4. In the list, locate the ECS. In the IP Address column, check whether the ECS has an EIP bound.
    • If no, check the next item.
    • If yes, unbind it.

      For details about how to unbind an EIP from an ECS, see Unbinding an EIP.

Checking Whether Security Group Rules Allow Traffic to and from the ECS Port

If the traffic to and from the ECS port is denied in the security group, add rules to the security group to allow the port traffic.
  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Elastic Cloud Server.
  4. On the Elastic Cloud Server page, click the name of the ECS.
  5. Click the Security Groups tab and view security group rules.
  6. Check whether you have configured inbound and outbound rules to allow traffic to and from the ECS port.
    • If yes, check the next item.
    • If no, click Manage Rule.

      On the Summary tab of the security group, click Inbound Rules or Outbound Rules to add an inbound rule and outbound rule that allow traffic to and from the ECS port. For details about inbound and outbound rule parameters, see Adding a Security Group Rule.

Checking Whether Network ACL Rules Allow Traffic in and out of the Subnet

Check whether the VPC subnet is associated with network ACL rules. If yes, check the network ACL rules.

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Click Service List in the upper left corner. Under Networking, select Virtual Private Cloud.
  4. In the navigation pane on the left, click Subnets.
  5. Check whether the NAT gateway subnet is associated with a network ACL.

    The specific network ACL name indicates that the association is successful.

    Figure 4 Network ACL
  6. Click the network ACL name to view the details.
    Figure 5 Network ACL details
  7. Check whether the inbound and outbound rules that allow traffic in and out of the subnet have been added.

    If no, add such inbound and outbound rules, or disassociate the network ACL from the subnet.

    For details, see Adding a Network ACL Rule and Disassociating a Subnet from a Network ACL.
    NOTE:

    The default network ACL rules deny all incoming and outgoing packets. After the network ACL is disabled, the default rules still take effect.

Checking Whether the EIP Bandwidth Limit Has Been Exceeded

If an EIP is bound to the public NAT gateway, the bandwidth is used to provide access traffic between the public network and the public NAT gateway.

If the network is disconnected, check whether the EIP bandwidth exceeds the limit.

For details, see How Do I Know If My EIP Bandwidth Limit Has Been Exceeded?

For instructions about how to increase the bandwidth, see Changing an EIP Bandwidth.

Checking Whether the SNAT Connection Limit for the Public NAT Gateway Has Been Exceeded

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Click Service List in the upper left corner. Under Management & Governance, choose Cloud Eye.
  4. In the navigation pane on the left, choose Cloud Service Monitoring > NAT Gateway.
  5. Locate the row that contains the public NAT gateway you purchased and click View Metric in the Operation column to check detailed monitoring.
    Figure 6 NAT gateway metric details
  6. Check whether the SNAT connection limit for the public NAT gateway has been exceeded.
    • If no, check the next item.
    • If the number of SNAT connections exceeds the upper limit of the public NAT gateway specifications, increase the specifications.

      For details about how to increase the public NAT gateway specifications, see Modifying a Public NAT Gateway.

Check Whether the Public NAT Gateway Status is Normal

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Click Service List in the upper left corner. Under Networking, select NAT Gateway.
  4. In the public NAT gateway list, locate the NAT gateway and check whether its status is Running.
    • If yes, check the next item.
    • If no, the possible causes are as follows:
      • The public NAT gateway is not renewed in time. Renew the subscription. For details about how to renew the subscription, see Making Repayments (Postpaid Direct Customers).
      • Your account or resources are frozen because you violated related security requirements or laws and regulations when using Huawei Cloud. If you complete the rectification within the required period and meet related security and legal requirements, your account and resources can be unfrozen. If you do not complete the rectification within the required period, your resources will be deleted.

Checking ECS Ports

Ensure that ECS ports are in the LISTEN state. Table 5 lists the common TCP statuses.

  • Linux

    Run the netstat -antp command to check whether the ECS port is in the LISTEN state.

    For example, run netstat -ntulp |grep 80.
    Figure 7 Checking port listening status (Linux)

    If no, enable the ECS port.

  • Windows

    Perform the following operations to check port communication:

    1. Run cmd.exe.
    2. Run the netstat -ano | findstr "PID" command to obtain the PID used by the process.
      For example, run netstat -ano | findstr "80".
      Figure 8 Checking port listening status (Windows)

      If no, enable the ECS port.

Table 5 Common TCP statuses

TCP Status

Description

Scenario

LISTEN

Listens for network connection requests from a remote TCP port.

The TCP server is running properly.

ESTABLISHED

Indicates that a connection has been set up.

A TCP connection is properly set up.

TIME-WAIT

Waits until the remote TCP server receives the acknowledgment after sending a disconnection request.

The TCP connection is disconnected, and this state is cleared in 1 minute.

CLOSE-WAIT

Waits for a connection termination request sent by a local user.

An application program fault leads to an open socket. This state is displayed after the network is disconnected, indicating that a process is in an infinite loop or waiting for certain requirements to be met. To resolve this issue, restart the affected process.

FIN-WAIT-2

Waits for the network disconnection request from a remote TCP server.

The network has been disconnected and requires 12 minutes to automatically recover.

SYN-SENT

Waits for the matched network connection request after a network connection request is sent.

The TCP connection request failed, which is generally caused by the delayed handling of high CPU usage on the server or by a DDoS attack.

FIN-WAIT-1

Waits for the remote TCP disconnection request, or the acknowledgement for a previous disconnection request.

If the network has been disconnected, this state may not automatically recover after 15 minutes. If the port has been used for a long period, restart the OS to resolve this issue.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback