Router tplink882 Virtual Server unreachable How to troubleshoot

Routers tplink882 solutions that virtual servers cannot access:

Possible reasons: How to access the server, or the address and port number entered when accessing the server is incorrect.

Solution: Access to the server depends on the actual application of the network access to the server and intranet access to the server is generally the same way.

The extranet user accesses the virtual server through the router WAN Port IP address (domain name), please confirm the Access server's browser or the client software to fill in the correct IP address (domain name) and the port, the following figure:

1, confirm the server network parameters

Possible cause: Incorrect server network parameters.

Workaround: Verify that the server network parameters are set correctly (IP address, subnet mask, default gateway), as shown in the following figure:

If the server is a host, determine the server through this router can be normal Internet.

2, to confirm the success of the server built

Possible cause: The server was not built successfully.

Solution: To confirm that the intranet computer can access the server, if the intranet is unable to access the computer successfully, we recommend troubleshooting server reasons.

3, shutdown firewall and anti-virus software

Possible causes: The server's firewall and antivirus software may be the extranet address as a trusted zone address, resulting in the extranet address can not access intranet servers.

Workaround: Shut down the server's system firewall and antivirus software.

1, check the virtual server rule settings

Possible cause: The server port or server IP address in the virtual server rule is filled in incorrectly.

Workaround: Confirm that the service port in the rule is the real port of the server, the IP address is the IP address of the server, and the corresponding rule status is in effect.

2, the DMZ host test

Possible reasons: The virtual Server rules open Server port is not complete, does not contain all the server's ports.

Workaround: Try to open the DMZ host test. In the Router management interface Click Forwarding Rules >> DMZ host, DMZ State Select Enable, DMZ host IP address input server IP address, click Save, the following figure:

If you open the DMZ host, the extranet can access success, it may be that some of the ports are not open caused. such as Network Camera and special application software (such as ERP system), if not clear Server service port, can consult server software service provider.

3, check the Internet control settings

Possible reasons: The router turned on the Internet control function, shielding the relevant port of the server.

Solution: Turn off the Internet control function and test. In the Router management interface click on the Internet Control >> rule management, do not tick open the Internet control, click Save, the following figure:

4. Remote Web Management

Possible causes: The router has remote Web management enabled, and the Web Admin port number conflicts with the virtual server port, causing the virtual server functionality to not function.

Workaround: Modify the Web management port differently from the Virtual Server service port, as shown in the following figure:

1, the service provider shield corresponding port

Possible reasons: Some broadband operators may block 80 of common service ports.

Workaround: Modify the service port (external port) for the operator Unshielded port, recommended to modify more than 9000, extranet users use the modified external port access server.

Note: Some routers do not support setting up service ports (external ports) and need to modify the server's service port.

2, WAN Port IP address is a public network IP address

Possible cause: The WAN port IP address is not a public network IP address and cannot be mapped to a virtual server.

Solution: The local area network's computer accesses the ip138.com, if looks up sees the IP address and the router WAN port IP address is different, proposed to contact the broadband service provider to solve the problem.

The Ip138.com page appears as shown in the following illustration:

Router WAN Port IP address (Run Status Page view in Router management interface):

3. DNS resolution issues (for domain name access only)

Possible cause: The router has successfully logged on to the dynamic domain name, the dynamic Domain name resolution IP address is not a router WAN port IP address, resulting in domain name inaccessible.

Workaround: The IP address of the dynamic domain name resolution of the network user is confirmed as the IP address of the router WAN port. Confirm method: Ping the Dynamic Domain name on the computer on the net, compare the IP address of the return with the IP address of WAN port. The following figure:

If the IP address contrast is different, you can try to modify the DNS server address of the extranet computer for 8.8.8.8 attempt.

Possible reasons: Intranet built for IPSec, FTP, VoIP and other special application servers, routers do not support the relevant ALG (application-level gateway).

WORKAROUND: Different routers may have different support for different types of ALG, and it is recommended that you contact router Vendor Technical support to confirm that the router supports the associated ALG.