Re: Web Hosting

From: Tony Su (anonymous_at_discussions.microsoft.com)
Date: 03/06/04


Date: Sat, 6 Mar 2004 14:42:45 -0800

Re-running the CEICW is not going to solve the problem...
it will just recreate the Companyweb site and point to it.

Depending on whether you are running ISA or not determines
what you need to do... plus additional issues like what
technologies you're using for you new website.

If you're not running ISA and are using ICF... you can
support HTTP host headers pointing to different sites, but
an ICF restriction is that all have to be bound to the
same LAN address. In this case, just configure your new
website in ISM for that LAN address using default port 80
with a unique Host Name.

If you're using ISA, if you can wait a couple days, I'm
nearly ready to re-publish my ISA recommendation after a
few touchups and adding screenshots. A few of the things
you can do following my recommendation...

- You can publish <any number> (unlimited!) number of HTTP
and HTTPS websites using a single WAN IP address as long
as they all share the same public FQDN. Examples...
https://www.yourdomain, https://companyweb.yourdomain,
https://bob.yourdomain can all be accessed on the same
single IP address. Note, you cannot do this using Host
Headers.
- Companyweb, Businesscard and custom websites can all be
accessed using standard ports, critical if your remote
Users are behind ISA and other application-level filtering
firewalls
- All websites are insulated against HTTP and HTTPS
attacks like NIMDA, even if the webservers are unpatched.

Many more benefits... I will update my recommendation at
my website shortly but the recommendation posted today is
<not> to be followed...

www.su-networking.com/faq/

Tony Su

>-----Original Message-----
>Rerun the CEICW... what options did you choose when
selecting what would
>be open from the outside?
>
>CSteck wrote:
>
>> I am trying to host a small public internet site on my
>> Small Business Server 2003. I have created a new web
>> site, and configured it correctly by all accounts. I
>> cannot seem to gain access to it from any machine
outside
>> of the domain. It works well on all machines inside of
>> the domain. It can be accessed via https and http on
>> client machines, but can only be reached via https from
>> outside machines. Any suggestions?
>
>--
>http://www.sbslinks.com/really.htm
>
>.
>



Relevant Pages

  • Re: SSL & SBS 2003 Std
    ... any HTTP IP Listeners you configure in IIS. ... If you decide to upgrade to ISA, this becomes trivial, since ISA can ... evaluate your host headers instead of IIS and re-direct to wherever you want, ... > You will have to publish the website on a different IP or port. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant get RTMP Macromedia Flash to play
    ... ISA as a web proxy only supports HTTP, ... the website owners have to follow the instructions ... I still can't get the videos to play. ...
    (microsoft.public.isa.configuration)
  • Re: HTTPS Using Web Proxy
    ... The ISA log displays the following on the error. ... HTTP Method = ... I created a HTPPS 444 protocol set to TCP port 444 and assigned it to my ... At first I was getting a error code: 502 Proxy Error and fixed that by ...
    (microsoft.public.isa)
  • Re: ADFS, ISA and SSL offloading
    ... I finally enabled logging on the ADFS ... Looking at this made me perform Link Translation in ISA and that's it, ... about it that is different than any normal SSL web app. ... embedded within the HTTP protocol. ...
    (microsoft.public.windows.server.active_directory)
  • Re: FrontEnd/BackEnd Vs ISA (reverse proxy)
    ... This is called SSL-bridging and you can configure it to be either HTTP or HTTPS ... A2 - Since ISA can cache some portion of the OWA pages, you get a performance gain by placing ISA between the ... site and a few remote site with a very a poor ... I have in DMZ an ISA Server used for reverse proxy. ...
    (microsoft.public.exchange.connectivity)