This step-by-step instruction guide describes how Internet Security and Acceleration (ISA) Server 2000 publishes multiple Web sites to the Internet. This guide uses one server running on Windows 2000 Server SP2 with Microsoft Internet Information Services (IIS) and a second server running Windows 2000 Server Service Pack 2 (SP2) and ISA Server.
For people to find Web sites on the Internet, the site's name must be associated with the public IP address of the ISA Server computer's external network adapter. The ISP or network administrator can help with this. DNS will typically have an entry for www.your-domain-name.com pointing to the ISA Server computer's external adapter.
To route requests for http://www.example.com/site1 to SERVER1 and requests for http://www.example.com/site2 to SERVER2, destination sets must first be created for each internal server. The Web publishing rules that are created later will link the URLs to the appropriate internal servers.
When people connect to the site, they do not see the server you published.
People who connect to the site may see a generic "under construction" page or nothing at all. This is most likely because IIS is running on the ISA Server computer itself. Requests to the site are then directed to IIS on the ISA Server computer. You should uninstall IIS from the ISA Server computer. The ISA Server computer should be running only ISA Server and nothing else.
You are trying to publish multiple sites, but they are not working correctly.
Make sure that you have your destination sets and publishing rules configured correctly. The destination set should specify your ISA Server computer's external name as the destination, along with a path that matches what you want people to type in their browsers when they want to access the corresponding internal server. The Web publishing rule should include the correct destination set and should refer to the correct internal server. Go back and look through the example in section 1. and pay particular attention to the dependencies.