Did the friends who opened the legend encounter the situation that the website could not be opened after building the website? I believe that there should be quite a lot of novice GMs who will encounter it. Today I will share with you the solution to the problem that the server IIS builds a website that cannot be opened from the external network.
First of all, there are 2 cases
01
The first is that both the external network and the server cannot be opened. What is the reason for this?
If you encounter a website that cannot be opened from the external network and the server, first check whether the steps of building the website are correct. If there is no problem, you can check whether the domain name has been filed, and whether the registered domain name has been resolved to the server. Above, the registered domain name is built on port 80. As long as the domain name is resolved to the server, there is basically no problem in building the website.
If you use an unregistered domain name, you can use a port other than 80 to build it, but the premise is that the server has opened the port permission other than 80, and you need to go to the server
Too much to contact the after-sales operation of the computer room, the domain name resolution is where the domain name is purchased, and the resolution operation is performed there
02
The second situation is that the server can be opened to browse the website, but the external network access of the computer cannot be opened. This is because the firewall of the server system is opened. Many Windows server 2008R2 systems have built-in firewalls. How to close the built-in firewalls? What about the firewall? Methods as below:
1. Click "Start" - "Administrative Tools" - "Advanced Tools Windows Firewall" in the lower left corner
2. The default is open before fire protection
3. Right-click and select "Advanced Security Firewall on Local Computer" in the upper left corner - "Properties" to open the property configuration, all of which are enabled by default
4. Modify the firewall status to "Off" , and then click the "Apply" button in the lower right corner
5. Then modify the "Domain Configuration File", "Private Configuration File", and "Public Configuration File" in turn, change the firewall status to "Close" , then click "Apply" , and finally click "OK"
6. At this point, the firewall has been closed!
For personal testing, you can completely turn off the firewall; if the server is used in a formal environment, it is recommended to turn on the firewall and set corresponding rules
The operation is too simple, so I won’t demonstrate it here