Build a Web server at home, the public network can not access
Hello everyone, someone has built a Web server, in their own home, and then through the public network IP address access.
I'm building it now. In the LAN can be accessed through the public network IP address, but the mobile phone (unicom 3G) access to the public network IP is not.
I have a peanut shell, peanut shell domain name in the home LAN can also access, but the use of mobile phone access to the domain name can not open the page.
Thank you for your understanding of the great God to help, help to see what is going on. Thank you!!
------to solve the idea----------------------
You should be able to access it outside the network.
There are also default 80 ports that are disabled, which are prohibited by telecommunications.
------to solve the idea----------------------
Home with a LAN IP bar, with a router to do port mapping
What is commonly called virtual server, mapping and other options, fill in the intranet ip,80 port, you can use the public IP access
------to solve the idea----------------------
Here are a few questions to keep in mind:
1, the local area network can not be exported to the LAN through the external network, so the test needs to be from the real external network access
2, from the 3G network can not access, can not explain any problems. Because DNS parsing takes time, parsing succeeds only if the domain name resolution is passed to your first-level DNS. The time required for this process depends on the frequency of access to the domain name in the same region, typically 3-5 days
3. At least for the time being, telecommunications is a ban on the behavior of such individuals providing web services.
4, peanut shell and other virtual domain name software, in the ADSL is effective. But in the community broadband is not necessarily, as long as there are routers in the middle, the virtual domain name is invalid
------to solve the idea----------------------
I tried a long time ago, I have seen some people say that the 80 port, in fact, said the closure of the 80 port should not be carefully tested.
I have been tested, our side of the Unicom is sealed according to the agreement, you can try, regardless of which port, your uplink data can be sent to your server, but your server downlink data is intercepted. Regardless of which port you are on, as long as your IP is not filed, the downlink information is all blocked.
Test code:
File_put_contents ('./test.txt ', $_server[' remote_addr '). " \ n ");
?>
If your situation is similar to mine, a Test.txt file will be generated in your program directory with the IP address of the client accessing your server.
------to solve the idea----------------------
Open the router's application server 80 port, and then use the local network IP can be accessed.
If your router is a one-of-a-kind cat, you need to go to the telecom to get your super admin password.
Dynamic IP can use dynamic domains such as peanut shells.
------to solve the idea----------------------
In the router do port insinuate Ah, the public network IP insinuate to your intranet IP.
------to solve the idea----------------------
May I ask what you are doing with this server?
------to solve the idea----------------------
It's best to use a peanut shell, to understand the principle, to understand the principle of hole-punching
