I set up my SBS 2003 server with ISA 2004. All service packs are installed.
The SBS server has two nics one of which has a public IP address.
I need to publish some internal websites for my customers and www.mysite.com:xx is not an option.
Is there any way I can manage to do this?
I understand the problem is that both IIS and ISA 2004 engage port 80 and 443 so that either you have your internal sites published or you SBS 2003 functioning.
I also tried httpcfg solution but it doesn't seem it's working, the w3 service starts but the standard SBS 2003 websites are not visible.
You need to use host headers to direct the incoming http request to the appropriate website. They'll each listen on the internal interface while your SBS listener is the ONLY thing listening on the external interface for port 80 and 443.
There are some very good tutorials, just search for the key words "host headers".
Thanks for your answer, I already know host headers and their use and maybe I didn't explain the problem well.
I have two sites on IIS 6 Windows 2003 on an internal server let's say 172.16.88.88.
I made 2 Web Publishing rules in ISA 2004 using the same Listener on port 80 (now there is a ISA 2004 process listening on port 80). The web sites are perfectly visible from both inside and outside the network.
Now I would like to publish two more IIS 6 sites on the same machine (SBS 2003) that holds ISA 2004 let's say 172.16.0.254 and another nic with public IP. For example OWA and the Sharepoint site.
I used httpcfg to let IIS listen only on the internal interface 172.16.0.254. In this way te sites are visible from the internal network.
Do I have to publish these two new sites with two web publishing rules that redirect external users to the internal IP of ISA 2004 machine?
By the way the Backup and Monitoring tools from the Server Management console are no longer working now with this configuration. I can't see the start page but if I browse them from IIS management I can see them!
You can't have two network cards with external IP's. This configuration isn't supported and won't work. Best to use the same IP and configure it the same way you did the others.
quote: Do I have to publish these two new sites with two web publishing rules that redirect external users to the internal IP of ISA 2004 machine?
Yes, if I recall correctly, but you'll still need another access rule if you're trying to publish on something other than the default web server "publishing.domain.local" for example. So you'll need one for the other domain name/IP.
hi to all. I use isa server 2004, the problem i have is that i want to redirect a specific site to a proxy server so that my clients can get access to site(my own internet gateway blocks the site and my clients need to access the site). what i decided is to add a web chaining rule to send speciefic sites to an upstream server(the desired proxy server).it worked but only for http requests ,and the site i need to access is https. finally i did not find what i want! would you please help me?
Hello Tom Thanks for you comment,but ISA Server dosen't redirect https sites at all. I checked chaining rule for http sites,it works correctly. but it seems that ISA Server dosen't undrestand https sites as usuall web sites to redirect them.
Hello, I found something else usefull for you to help me. in the web chaining where i should add https://* ,isa server has said in the dialog : "URLs included in this set(applicable for HTTP trafic only)"
This shows that we have no way to redirect non-http web sites.