Web publishing scenarios
The Web publishing functions of Microsoft Internet Security and Acceleration (ISA) Server benefit organizations that want to securely publish Web content from within their protected intranet. ISA Server can protect an organization's Web server that is hosting a commercial Web business or providing access to business partners. The ISA Server impersonates a Web server to the outside world, while the Web server maintains access to internal network services.
The Web server you are publishing can be located either on the same computer as ISA Server or on a different computer.
Configuring the ISA Server computer
Regardless of how you set up the Web publishing scenario, ISA Server must be configured to listen for incoming Web requests. The incoming Web request properties specify which IP addresses and ports on the ISA Server computer listen for incoming Web requests. The incoming Web request properties also determine the necessary authentication required when accessing internal servers.
Configuring DNS server
When you publish Web servers, external clients may need to resolve their names, using the internal DNS server. As such, the internal DNS server is itself a publishing server. If the DNS Server is a SecureNAT client, then no configuration is required. After you install ISA Server, create a server publishing on the ISA Server that publishes the DNS Server. For more information on server publishing rules, see the on-line help provided with ISA Server.
The following sections detail network configurations for Web publishing scenarios.
The following sections describe Web publishing scenarios:
| • | |
| • | |
| • | Using packet filters to publish a Web server on the ISA Server computer |