Regarding your application setup --
As soon as you have a server, I would suggest that you PUBLISH websites
hosted on the Pro machine to the server -- instead of trying to have the
server RequestForward to the Pro machine.
i.e. It's usually better to publish websites to the server instead of asking
the server to RequestForward or 302Redirect. In the 302Redirect case, the
Pro machine's IP needs to be exposed to the Internet, which you may not
want. In the RequestForward case, IIS doesn't support this capability
natively, it is poor performance, and indirectly exposes your Pro machine to
the Internet (so you need to secure both the Pro and Server machines).
If you publish websites to the Server machine, you secure one machine and
incur no extra network traffic.
I understand that people like to take a machine, "set it up" with an
application, and then want to "publish" this machine and its application to
the Internet -- while "easy" conceptually, it is short-sighted from a
manageability, performance, and security perspective.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"scott" <scottscottland.DeleteThis@yahoo.com> wrote in message
news:%239u0JO5nDHA.2652@TK2MSFTNGP09.phx.gbl...
Hi,
How do I go about having 2 or 3 machines running IIS behind window 2000
server on the same public IP (i.e accessible from net) ?
CURRENT SETUP
Net connection to router - router ports as follows:
1 port goes to existing IIS on window 2000 pro.
1 port goes to firewall and internal LAN.
Im going to insert a windows 2000 server between the existing router and the
current IIS machine. This server will run IIS. I also need allow net
traffic to access an internet on the windows 2000 pro machine behind the new
2000 server and also any other machines that i may need to add (i.e
developing web based apps so will need to add remove servers as needed).
Thanks for any pointers.
Scott.
>> Stay informed about: how to add IIS machines behind existing IIS setup ? 
FAQ
Profile
Private Messages
Log in
