Hi,

I would like to add a second IIS machine in my DMZ. All HTTP traffic
currenly hits port 80 on my router and is forwarded to IIS1.

If I setup the following can I run another IIS machine side by side:

1. setup url  www.domain.co.uk and direct to my IP
2. direct port 999 on router to IIS2
3. enter www.domain.co.uk:999 in a web brower to hit IIS2.

Will this work ?

Do I also need to configure IIS2 to listen for incoming HTTP traffic on port
999 ?

If so how ?

Thanks for your time.
Scott.

[ Post a follow-up to this message ]

"scott" <scottscotland@yahoo.com> wrote in message
news:%23ycEWxH$DHA.2520@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> I would like to add a second IIS machine in my DMZ. All HTTP traffic
> currenly hits port 80 on my router and is forwarded to IIS1.
>
> If I setup the following can I run another IIS machine side by side:
>
> 1. setup url  www.domain.co.uk and direct to my IP
> 2. direct port 999 on router to IIS2
> 3. enter www.domain.co.uk:999 in a web brower to hit IIS2.
>
> Will this work ?
>
> Do I also need to configure IIS2 to listen for incoming HTTP traffic on
port
> 999 ?
>
> If so how ?
>
> Thanks for your time.
> Scott.

Yes, that should work, and yes you have to configure IIS2 to listen on port
999, otherwise, it'll probably default to port 80 on whatever that machine's
IP address is.

[ Post a follow-up to this message ]

"scott" <scottscotland@yahoo.com> wrote in message
news:%23ycEWxH$DHA.2520@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> I would like to add a second IIS machine in my DMZ. All HTTP traffic
> currenly hits port 80 on my router and is forwarded to IIS1.
>
> If I setup the following can I run another IIS machine side by side:
>
> 1. setup url  www.domain.co.uk and direct to my IP
> 2. direct port 999 on router to IIS2
> 3. enter www.domain.co.uk:999 in a web brower to hit IIS2.
>
> Will this work ?

It should, assuming your router was set up correctly.  (I can do it on my
crappy little home Linksys router, so I assume any real router can do it
too.)

>
> Do I also need to configure IIS2 to listen for incoming HTTP traffic on
port
> 999 ?

Yes, if you do not translate it back to a different port.
>
> If so how ?

You can specify the port a virtual web should listen on in the setup wizard
or in the properties.  (Same place you specify the IP and host header.)

>
> Thanks for your time.
> Scott.
>
>

[ Post a follow-up to this message ]

Thanks very much : )

Scott.

[ Post a follow-up to this message ]

one quick addtional thing:

Im lead to believe that using host headers you can manage all traffic for
multiple IIS machines on port 80. Is this the case ?

for example:

net
v
router
v
iis1 > iis2
v
iis 3

You would manipulte host headers on IIS 1 to direct traffic on port 80 to
IIS2 or IIS3 depedning on what the clinet is requesting ?

Thanks
Scott.

[ Post a follow-up to this message ]

Xref: TK2MSFTNGP08.phx.gbl microsoft.public.inetserver.iis:299987


"scott" <scottscotland@yahoo.com> wrote in message
news:OY9g2KI$DHA.2072@TK2MSFTNGP11.phx.gbl...
> one quick addtional thing:
>
> Im lead to believe that using host headers you can manage all traffic for
> multiple IIS machines on port 80. Is this the case ?
>
> for example:
>
> net
> v
> router
> v
> iis1 > iis2
> v
> iis 3
>
> You would manipulte host headers on IIS 1 to direct traffic on port 80 to
> IIS2 or IIS3 depedning on what the clinet is requesting ?
>
> Thanks
> Scott.
>
>

Host headers allow traffic on a single IP and the same port to get different
web pages.

Each machine with IIS still needs it's own IP address, from there you can
share it with different webs.

Though if your router can translate ports 80, 81, and 999 to IP1, IP2 and
IP3 respectively all using a single WAN IP your example above might work.

[ Post a follow-up to this message ]