Re: HOW MORE FRUSTRATING CAN THIS GET!!!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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

Date: Tue, 8 Jun 2004 14:49:10 -0700

Hello Claus,

Here, let me cut through the confusion...

First, I'm going to assume that you're working on an
SBS2K3 although you referred to an SBS2K in your original
post... Big difference!

Because the underlying security of Win2K and Win2K3 and
the IIS architecture is so different on each version of
Windows, you're dealing with completely different
procedures and requirements.

Before going further, and again assuming you're working on
a SBS2K3, this is the reason why you are experiencing the
problems you're seeing...

Win2K3 (and SBS2K3) IIS security changed fairly
dramatically. By default, unless IIS is configured for
socket pooling, IIS will listen on only specific IP
addresses and no other.

But, SBS2K3 takes this a step further beyond Win2K3...
during the SBS2K3 setup, it runs a special utility called
SBSIISCONFIG which locks down IIS to one and only one IP
address... the primary LAN address.

So, this is your starting point. You will find that a
default SBS installation does not support IIS websites on
any IP address except for its LAN address.

You now have two main avenues to deploy websites besides
what is installed by default...

1. Deploy all other websites on the same LAN IP address
and use IIS Host Headers (most often the preferred
solution) or non-default ports to differentiate each
website. This solution works well for most Web Publishing
scenarios if you use FQDN in your Destination Set and in
the Action Tab specify the Hostname of your Virtual Website
(If you use non-default ports there are ISA issues, so
post again if you really need to use that method instead
and a full explanation will be given).

2. Because of various reasons, using Host Headers can be
insufficient (ie. does not support SSL, some apps need to
connect to individual IP addresses, maybe your
preference). If you decide you need to deploy your Virtual
Websites on individual LAN IP addresses... <or> if you
want to deploy your website with a WAN IP address... then
you have to undo the configuration created by SBSIISCONFIG
and use normal Win2K3 tools like HTTPCFG to configure your
IIS IPlisteners. To do this, I have published a lengthy
series of procedures with screenshots...

www.su-networking.com/faq/
(click on first link)

HTH,
Tony Su

>-----Original Message-----
>thanks for answering. I will watch the newsgroup.
>
>Beside the packe filters I thought I also need to add the
IP to the list of
>addresses for incoming requests. Is that correct?
>
>"Phillip Windell" <@.> wrote in message
>news:uWBqVnVTEHA.3752@TK2MSFTNGP12.phx.gbl...
>> Ok. I would think Packet filters for allowing http is
all that is needed
>> but I have no experience with SBS. Stick around I know
that there are
>some
>> guys here that know SBS pretty well and they would know
what to do. If
>not
>> then you may also want to post in one of the SBS Groups
as well,...just
>make
>> sure they understand that this is the SBS with ISA
rather than the
>variation
>> that doesn't come with it.
>>
>> --
>>
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>>
>> "cjobes" <cjobes@nova-tech.org> wrote in message
>> news:uYdMTiRTEHA.3332@TK2MSFTNGP12.phx.gbl...
>> > I would like to run that website ON the ISA. It
doesn't have to be
>BEHIND
>> > it. As I explained in my original post, it's a
SBS2003 box that has all
>> > server components on the same computer. This site has
nothing to do with
>> the
>> > rest of the SBS2003 setup. The SBS2003 domain is
abc.com with its own
>> > website and the additional website is www.def.com. I
just want to use
>the
>> > same box to host that site with a second IP address -
basically telling
>> the
>> > ISA to ignore it and just serve it to the internet.
>> >
>> > Is that possible?
>>
>>
>
>
>.
>

Relevant Pages

  • Re: IIS Stopped working properly.
    ... SBS 2003 brings a full working IIS, and it even includes some default websites like the Remote Web Workplace or the Outlook Web Access that are meant to be used from the outside. ... You can easilly configure other websites and publish them to be access from the outside, despite the advised action would be having another server inside running IIS and having the SBS 2003 machine forwarding these extra webistes requests to it. ...
    (microsoft.public.windows.server.sbs)
  • Re: cannot access site by IP - bad request invalid hostname
    ... You call the above two websites, but from IIS perspective, it is one website ... Request", ... The xxx.xxx.xxx.69 was setup initially with the server setup. ...
    (microsoft.public.inetserver.iis)
  • Re: ISS problem
    ... It sounds like you are running Small Business Server. ... IIS will keep backup copies of its configuration (check in the IIS Manager ... Since they are independent websites, ... sure that both websites do NOT share the same IP, Port, and Host header. ...
    (microsoft.public.inetserver.iis)
  • Re: Virtual directories in IIS
    ... This really isn't an issue with IIS but rather names. ... You are authoring HTML, and this is simply how HTML works. ... Your concept of "lock everything within my virtual folder" has absolutely no ... you can certainly run custom applications that "rebase" websites ...
    (microsoft.public.inetserver.iis)
  • Re: IIS reports SmartNav.htm as a 404 File Not Found, Why So?
    ... If you point websites to different physical partitions, ... If so, fix that. ... > IIS ...
    (microsoft.public.dotnet.framework.aspnet)