Setting up Multiple IP Addresses (Windows 2000 Server)
Windows 2000 TCP/IP Implementation:
This is a fairly basic walkthrough and shouldn't need much
explaining. Multiple IP addresses are one of the methods
of hosting a number of web sites on a single IIS Server. Headers (as used by Hosting Providers) are the preferred method.
1. Where to find your Network settings dialogue.
I know it may sound obvious, but if not right-click
on 'My Network Places' and select 'Properties'.
2. Opening your local area connection properties:
To open the network properties dialogue, right-click
on 'Local Area Connection' and select 'Properties'.
3. Internet Protocol (TCP/IP):
Ignore everything else and select 'Internet Protocol
(TCP/IP)' and click 'Properties' as shown in Fig.3 above.
4. What's my IP???:
Don't worry about this dialogue, just click 'Advanced'
to get the next one. For your information though, the
Default Gateway shown is my router and the two DNS servers
belong to BT.
5. Adding extra IP addresses:
As you can see, I'm using the Win2K style 10.0.X.X IP
addresses rather than the typical 192.168.X.X WinNT
type. It doesn't really make any difference for this
Adding extra IP addresses is simple, just click add,
enter the IP address (as shown) and corresponding Subnet
mask. My network is only likely to use only a few IPs
so I'm going to mask out all but the last 255 as shown.
That's it really, if you want to add a few more IP addresses,
just repeat this step until you have all you need. When
you set up a new site in IIS you'll be able to select
the IP you want to use from a list (see configuring
IIS5 to host your intranet) and accessing your site
from your internet network through Explorer is simply
a case of typing that IP in... a site using the IP we've
just created would be http://10.0.0.2/
Two final notes though...
In my network, 10.0.0.1 is the IP of fuser1, our main
server. Fuser2 uses 10.0.0.2 and Fuser3 10.0.0.3..etc...
it's probably a better idea to use IP addresses that
aren't likely to be specified by your server farm (now
or in future) so 10.0.0.100, 10.0.0.101 and so on...would
be pretty safe bets....
If you've arrived at this page from my 'Configuring
IIS5 to host your Intranet' page then please bear in
mind that these pages were written more than four months
apart and since then, both my network and IP configurations