Installed AppServer 127.0.0.1 can access, but with the external network IP access is not
Ask how to set up with my own IP access, because the extranet has personal like access. I used to be able to IIS, APACEH.
------Solution--------------------
If it is a local area network, let the other side in the host to bind your IP
------Solution--------------------
Port Mappings on routers
The specific configuration is as follows
Our local Web server is generally Http://localhost/or behind with ports, LAN users are through the computer's intranet IP access to the Web server, for example, the IP of the Web server computer is 192.168.1.112, other users within the LAN can be http://192.168.1.112 access to our Web server, but for extranet users, it is not possible to access our Web server by accessing the http://192.168.1.112 IP. Then you need one. For extranet users, your Web server is the only IP address, and the only IP address that works is your route.
Here I take tp-link route as an example, describes how port mapping operation (Welcome to shoot bricks).
We go into the router and look at the IP address of our routed WAN port.
WAN Port
This IP (27.40.127.248) is an extranet user can uniquely identify your computer address of the routing ip, but a route is generally connected to several computers at the same time, how to let visitors find you, this needs to port mapping.
Port mappings are also known as Port forwarding. The port mapping process is like your home in a Community T Building Room 112, your friend came to you, find the door of the community, do not know which floor you live? Ask the Community security, security told him your house detailed number, so that your friend very easy to find your home. This security is on the router, this process is the external network access through the port map image metaphor.
Then we find its port mapping function in the Tp-link route, the port mapping is located in the "forwarding rules" inside the "virtual server" (each brand of the name of the route is not the same, please find out in detail), and then add the forwarding entries, such as:
Virtual Services
80 Port Forwarding
Under my tp-link, I've added two entries, Just 80 ports and 8080 ports are forwarded to the intranet 192.168.1.112 on the PC, and now as long as the user accesses the routed IP via 80 or 8080 ports, the route will turn the user to the local server where the computer is located 192.168.1.112.
Port mappings
In addition to the Web server can do such settings, FTP can also do similar forwarding, the default port of FTP is 21.
------Solution--------------------
I suggest you check out the peanut Shell tool.
------Solution--------------------
Port 80 is sealed by telecom, try another port.
