Help with IIS 6.0 and port mappings

Hi David,

is this related to the following quirk:

I have three HTTP websites:

10.0.0.1:80
10.0.0.2:80
10.0.0.1:8504

To successfully configure httpcfg for these three I have to do the
following:
httpcfg set iplisten -i 10.0.0.1:80
httpcfg set iplisten -i 10.0.0.2:80

And everything works fine, except that 10.0.0.2:8504 is active and listening
(I haven't figured out what is listening, since all requests return Bad
Request (Invalid Hostname).)

I tried to get around this by using httpcfg:
httpcfg set iplisten -i 10.0.0.1:8504

but at this point all webserver fail to start.

Troubleshooting this is driving me nuts! And currently I'm only working
with 3 websites and two IP addresses. I'm about to implement a production
box with about a dozen IP addresses, similar number of websites, plus
additional (non IIS) based services... Then I'm going to confuse it all and
use NLB... (Hence the experimentation now)

Are quirks like these going to be cleaned up any time soon?

Thanks
Craig


"David Wang [Msft]" <someone.RemoveThis@online.microsoft.com> wrote in message
news:uP1A3UZlEHA.3720@TK2MSFTNGP12.phx.gbl...
 > Unfortunately, this is a current limitation in HTTP.SYS with no
 > work-arounds. The other major limitation (also no workaround) is that if
 > you specify port 80 as HTTP and 443 as SSL for one IP, you cannot choose
 > port 80 as SSL and 443 as HTTP on another IP.
 >
 > When IIS configures HTTP.SYS with a list of IP:Port:Host bindings that
 > represent IIS websites, HTTP.SYS binds to all possible combinations of the
 > collective IP/Port possibilities regardless if there is an actual IIS
 > website. If there isn't a website configured for the combination,
HTTP.SYS
 > returns a 400 -- but this still prevents you from binding something to
that
 > particular IP:Port combination.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Help with IIS 6.0 and port mappings 

I don't have an immediate answer. I am asking the team responsible for
HTTP.SYS and httpcfg about their plans.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Craig Humphrey" <craig.humphrey DeleteThis @nospam.chapmantripp.com> wrote in message
news:OwsGFDfoEHA.2852@TK2MSFTNGP09.phx.gbl...
Hi David,

is this related to the following quirk:

I have three HTTP websites:

10.0.0.1:80
10.0.0.2:80
10.0.0.1:8504

To successfully configure httpcfg for these three I have to do the
following:
httpcfg set iplisten -i 10.0.0.1:80
httpcfg set iplisten -i 10.0.0.2:80

And everything works fine, except that 10.0.0.2:8504 is active and listening
(I haven't figured out what is listening, since all requests return Bad
Request (Invalid Hostname).)

I tried to get around this by using httpcfg:
httpcfg set iplisten -i 10.0.0.1:8504

but at this point all webserver fail to start.

Troubleshooting this is driving me nuts! And currently I'm only working
with 3 websites and two IP addresses. I'm about to implement a production
box with about a dozen IP addresses, similar number of websites, plus
additional (non IIS) based services... Then I'm going to confuse it all and
use NLB... (Hence the experimentation now)

Are quirks like these going to be cleaned up any time soon?

Thanks
Craig


"David Wang [Msft]" <someone DeleteThis @online.microsoft.com> wrote in message
news:uP1A3UZlEHA.3720@TK2MSFTNGP12.phx.gbl...
 > Unfortunately, this is a current limitation in HTTP.SYS with no
 > work-arounds. The other major limitation (also no workaround) is that if
 > you specify port 80 as HTTP and 443 as SSL for one IP, you cannot choose
 > port 80 as SSL and 443 as HTTP on another IP.
 >
 > When IIS configures HTTP.SYS with a list of IP:Port:Host bindings that
 > represent IIS websites, HTTP.SYS binds to all possible combinations of the
 > collective IP/Port possibilities regardless if there is an actual IIS
 > website. If there isn't a website configured for the combination,
HTTP.SYS
 > returns a 400 -- but this still prevents you from binding something to
that
 > particular IP:Port combination.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Help with IIS 6.0 and port mappings 

Ok, they said that httpcfg only specifies specific IP to listen on -- not
IP:Port combination. Thus, when you added the second entry for
10.0.0.1:8504 , it's as if you added a second entry for 10.0.0.1 -- which is
then considered a conflict.

So in your case, you would configure IPListen for two IPs, 10.0.0.1 and
10.0.0.2, and in IIS Maneger configure your three websites. Due to how
HTTP.SYS currently works, 10.0.0.2:8504 cannot be bound to another server -
only an IIS Website can be bound to it, and it has to be the same HTTP/HTTPS
as 10.0.0.1:8504.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"David Wang [Msft]" <someone RemoveThis @online.microsoft.com> wrote in message
news:u8DjdR5pEHA.644@tk2msftngp13.phx.gbl...
I don't have an immediate answer. I am asking the team responsible for
HTTP.SYS and httpcfg about their plans.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Craig Humphrey" <craig.humphrey RemoveThis @nospam.chapmantripp.com> wrote in message
news:OwsGFDfoEHA.2852@TK2MSFTNGP09.phx.gbl...
Hi David,

is this related to the following quirk:

I have three HTTP websites:

10.0.0.1:80
10.0.0.2:80
10.0.0.1:8504

To successfully configure httpcfg for these three I have to do the
following:
httpcfg set iplisten -i 10.0.0.1:80
httpcfg set iplisten -i 10.0.0.2:80

And everything works fine, except that 10.0.0.2:8504 is active and listening
(I haven't figured out what is listening, since all requests return Bad
Request (Invalid Hostname).)

I tried to get around this by using httpcfg:
httpcfg set iplisten -i 10.0.0.1:8504

but at this point all webserver fail to start.

Troubleshooting this is driving me nuts! And currently I'm only working
with 3 websites and two IP addresses. I'm about to implement a production
box with about a dozen IP addresses, similar number of websites, plus
additional (non IIS) based services... Then I'm going to confuse it all and
use NLB... (Hence the experimentation now)

Are quirks like these going to be cleaned up any time soon?

Thanks
Craig


"David Wang [Msft]" <someone RemoveThis @online.microsoft.com> wrote in message
news:uP1A3UZlEHA.3720@TK2MSFTNGP12.phx.gbl...
 > Unfortunately, this is a current limitation in HTTP.SYS with no
 > work-arounds. The other major limitation (also no workaround) is that if
 > you specify port 80 as HTTP and 443 as SSL for one IP, you cannot choose
 > port 80 as SSL and 443 as HTTP on another IP.
 >
 > When IIS configures HTTP.SYS with a list of IP:Port:Host bindings that
 > represent IIS websites, HTTP.SYS binds to all possible combinations of the
 > collective IP/Port possibilities regardless if there is an actual IIS
 > website. If there isn't a website configured for the combination,
HTTP.SYS
 > returns a 400 -- but this still prevents you from binding something to
that
 > particular IP:Port combination.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Help with IIS 6.0 and port mappings