Re: [OT] IIS, domains, routers and host headers

["Steve Norman" <steve@xxxxxxx>]

In the TCP/IP Properties for the Network Connection click on Advanced, the
first window you can see allows you to add multiple IP Addresses to a
single
card.

Once IP Addresses are configured if you open up the properties for the
default website you can set the IP address on the Web Site tab.  When you
add another web site, you should get the option to configure which IP
address to use.

Steve

----- Original Message -----
From: "Paul Gale" <groups@xxxxxxx>
To: <ukha_d@xxxxxxx>
Sent: Friday, August 29, 2003 4:56 PM


Ah ok - Where and how do I set an additional IP address for the server
(only
one n/w card?)

Cheers,

Paul.


-----Original Message-----
From: Steve Norman [mailto:steve@xxxxxxx]
Sent: 29 August 2003 16:31
To: ukha_d@xxxxxxx

The easiest way is to assign multiple internal IP addresses to the server.
Inside IIS you can bind a website to a specific IP address rather than all
of the IP addresses on the server.

Steve

----- Original Message -----
From: "Paul Gale" <groups@xxxxxxx>
To: <ukha_d@xxxxxxx>
Sent: Friday, August 29, 2003 3:14 PM
Subject: [ukha_d] [OT] IIS, domains, routers and host headers


I think that only covers a small area ;)

I need some help with my home/office network setup or some pointers to good
resources where I can research the answers:

I currently have a W2K server running on my network using a 192.168.0.x
address. My ADSL router is setup to route one of my public IP addresses and
associated domain names through to the server (but only allows port 80
through). The website does not have anonymous access and file security on
all files is set to Administrator and one internal domain user. AD is
running. I have several HA and alarm pages and OWA setup on this web server
so want to keep it as secure as possible. I currently only have one default
web site setup on port 80. My internal domain is set to home.local and the
server and other servers on the network appear as homeserver.home.local,
cameraserver.home.local etc. I have a DNS server running on this server too
and all clients point to this before my ISP DNS servers.

I’d also like to use this server as a testing server for developing
web
pages and applications. I don’t want this site to be accessible from
the
Internet at all (or at the very least, protected). What’s the best
way of
doing this? Would host headers help??? (I don’t know anything about
them).

My IIS knowledge is reasonably basic.

Ta,

Paul.





** UKHA2004 BE THERE! ** - start planning now.

http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




** UKHA2004 BE THERE! ** - start planning now.

http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/






** UKHA2004 BE THERE! ** - start planning now.

http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/