Solution to the problem that the Nexus service on port 8081 of the TP-Link router cannot be accessed through the Internet

Solution to the problem that the Nexus service on port 8081 of the TP-Link router cannot be accessed through the Internet

Solution to the problem that the Nexus service on port 8081 of the TP-Link router cannot be accessed through the Internet

Environment Description:

Router: TP-Link TL-R478G +
Intranet server information:
IP: 192.168.1.221
System: CentOS 6.5
Service: Nexus
Port 8081

Ing method:

Problem description:

Services on other servers can be accessed through the Internet IP address through this ing method, but this is not the case. It is useless to try to change multiple ports during the ing.

Problem Analysis:

The initial analysis should be about the network configuration of the mapped server!

Solution:

Check Network Configuration:
Vi/etc/sysconfig/network

Two lines in the red box are missing in this file configuration!

Vi/etc/sysconfig/network-scripts/ifcfg-eth0

The gateway here is different from the actual one.

After both are corrected, restart the network configuration.
Service network restart

Use an Internet IP address for access. Haha, the problem is solved.

Note:

In my environment, the Intranet gateway is 192.168.1.2, usually 192.168.1.1.

Other solutions

1. First, check whether the Intranet Service is normal;
The Intranet IP address of the internal Netcom server to test whether the corresponding service can be accessed. If the Intranet cannot be accessed normally, we recommend that you check the causes of the Intranet, for example, whether the host is configured correctly and whether the Intranet client can successfully Ping the host, ensure that the service host can connect to the Internet normally.
2. Check whether the Internet address is restricted;
Connect the server to the Internet without passing through the router and test whether the Internet can be accessed. If the access fails, the network operator may have blocked the port to be mapped and the Internet cannot access the mapped port. Contact the carrier for details.
3. Check whether the Internet cafe router settings are normal:
1. First, check whether the port ing configuration is correct. For specific port ing configurations, refer to "Procedure for Internet cafe route ing".
After confirming that the configuration is correct, you can enable port backflow in basic settings-basic options to enable Intranet Communication's Internet IP address (the Internet IP address is in the system status → Network Interface query ), test whether the ing port can be accessed.
2. Network Security → AttacK Defense → Internet defense → disable External Open Port Protection → disable blocking of Internet requests → save
3. Check whether the vro port conflicts with the ing port in system tools management options.
4. If the Internet is a dual-line access, check whether the accessed Internet IP address corresponds to the corresponding ing line. Or whether the user has made a source address route to direct the server to another line, but not the same line as the ing line.
5. If the Internet is single-line access, check whether a pair of IP addresses of the corresponding Internet interface are occupied by NAT, resulting in Port ing failure.
4. Others
1. Make sure that the above steps are correct. If not, disable anti-virus software and firewall on the server.
2. If the Internet checks that the specified port has been mapped successfully but cannot be accessed, use the one-to-one NAT Function to map all the ports on the server and check whether there are other ports to be mapped.