Bottom: In Windows Serverserver, deploying applications such as HTTP when the protocol application, when the external Netcom HTTP protocol to access the Web page, we need to get the server entry permission, in the visitor's browser page content enough talent normal display, besides. It cannot be displayed correctly. The results are similar for example to the following:
Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvbgvqdw8=/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70 /gravity/center "height=" 177 "width=" 374 ">
So. How do I establish an inbound rule for a normal Web page?
Usually, when you test a site. We'll disable Windows Firewall. After all, the firewall has been disabled and all access has become without resistance. For example, as seen in:
Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvbgvqdw8=/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70 /gravity/center "height=" 268 "width=" 510 ">
And when we formally deploy the site, Windows Firewall should still be enabled, and only by setting some rules for access to the program and Web pages can be properly interviewed.
Setting up access rules is easy, in Control Panel \ Windows Firewall \ Advanced settings. Add an inbound rule to it. ( This example takes Windows Server R2 as an example )
Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvbgvqdw8=/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70 /gravity/center ">
All the way to the default selection, the next step can be followed. Server program and port it can exceed normal access.
Copyright notice: This article Bo Master original article. Blog, not reproduced without consent.
Windows Server licensing port or execution tips