you did not say if the second server is on another machine or not. If it is
on the same machine and the same IIS server, you will have to use host
headers to keep the different domain name/websites to use the same ip
address, this is the easiest method (except host headers do not support ssl)
If the new server is on another machine that uses port 80 and if you can
control the domain names, you might want to consider port mapping. However,
you take a chance of the outside not being able to get to the server on any
other port than 80.
an example config:
I have 2 machines with web servers at my home.
My outside ip is dynamic, I use no-ip.com for this:
mrmad.no-ip.com -> 24.202.251.49
my router directs port 80 on 24.202.251.49 to 10.0.0.10 port 80 my win2k
machine
hotwiz.no-ip.com redirects to mrmad.no-ip.com port 8888
my router redirects port 8888 on 24.202.251.49 to 10.0.0.15 port 80
this is my Linux box
so if in internet explore I type <a style='text-decoration: underline;' href="http://hotwiz.no-ip.com" target="_blank">http://hotwiz.no-ip.com</a> , I get the web
site on the Linux box, however, if I was outside in the internet and I was
using a web browser somewhere where port 8888 is blocked, I would result in
an dns error.
I have one production server that is hosting 3 different web sites on the
same machine, same ip address, all on port 80, host headers on the iis
server make this possible.
--
And if you have time, check out my new website:
<a style='text-decoration: underline;' href="http://hyman.sytes.net" target="_blank">http://hyman.sytes.net</a>
"marcus lee" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
news:1621601c41e87$465a7c90$a001280a@phx.gbl...
> i am running one IIS web server in a small office, and am
> setting up another web server running for testing
> purposes. if the first web server defaults at port 80 on
> my firewall, how should I configure access to the second
> web server?
>
> thanks<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: multiple web servers under one IP