RE: IIS/Company Web question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

That's great! The combination of using ISA and host headers along with the
2 different public host names should work out very well for you.

I would start out by running the CEICW if you haven't already done that.
During that process it will ask you which common web services you want to
publish. I would publish the common ones...OWA RWW, etc. I would not
choose to publish 'Business Web site (wwwroot)'. The latter makes the
assumption that it will be published on the default website. On the next
screen of the wizard it will ask you for a web certificate. Here you
should specify the public URL that someone would enter to get to secure
internal websites like OWA. This would probably be 'mail.mywhatever.com'.
By the way, I am making an assumption at this point that the public website
will not require SSL. If it will, let me know and we will have to make
some alterations. Choose the appropriate options in the remaining windows
and complete the wizard.

Once the wizard is complete verify that typical web services like OWA and
RWW work.

Next, create your public website. You can create just a skeleton 'under
construction' for now.

Open the ISA console, expand the server, right-click the 'Firewall Policy'
node, and select New, Web Server Publishing Rule. Give it a name. Choose
'Allow'. On the 'Define Website to Publish' page specify the server's
internal IP address, check the box for 'Forward the original host
header...' and for the 'Path' type "/*" (without the quotes). On the next
screen type the public URL (www.mywhatever.com) and leave the path as "/*".
For the Web Listener select the 'SBS Web Listener'. Let it default to
'All Users' on the next page. Click Finish. This will create your basic
web publishing rule for the web site. To fine-tune the rule simply go to
its properties under the 'Firewall Policy' node. Common settings you might
need to tweak are:
- under the "To" tab change from "Requests appear to come from the ISA
Server computer" to "Requests appear to come from the original client"
- under the 'Public Name' tab you could additional websites and IP
addresses in the future;
- under the 'Paths' tab you add, remove, or modify paths on the website
that you want to publish

Most of the settings should be OK.

Let me know if you have questions with any of this.

Jim




.

Relevant Pages

  • Re: New Thread for Tony Su
    ... I have the need to publish a website on the server that is totally unrelated ... So I added the 251 IP to the WAN interface for that, ... Then I added a publishing rule to the ... ISA to forward all HTTP traffic on 251 to this LAN interface. ...
    (microsoft.public.isa)
  • Re: DNS www record to external IP - Where to ADD???
    ... I'm stumped about why I cannot access my externally hosted website. ... know ISA, but I can't see this being anything but an ISA problem. ... Start the DNS Management console by Start> Programs> ... Right click the domain name folder and select New Host from the ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA and internal webs
    ... On the assumption that you're trying to use the same base URL as for the SBS remote access stuff, the URL you quote is rejected by ISA unless you chose to publish the "business card website" in the CEICW. ... If you choose to web publish using a subdirectory, you should use the existing SBS web listener in your publishing rule. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Web Server
    ... you would need port 80 inbound open. ... ISA is a firewall, which helps you ... For details about how to host a website, ...
    (microsoft.public.windows.server.sbs)
  • Re: iptables and port scan
    ... >> offered to the internet by a given host. ... >On this website, you'll find links. ... >mentionned, if I offer FTP, it will be mentionned, and so on. ... http://www.mixmaster.anonymizer.com/ first and search for a permit? ...
    (comp.security.firewalls)