1. Place the slave servers in a network using private IP addresses
2. Add a second card to the master server, with a private address, connected
to the network of slave servers.
3. Configure NT to allow routing between the cards.
4. Configure your apps accordingly.
Used a similar solution here, for WMedia streaming. I didn't want the
clients to be able to connect directly to the encoders.
Brian Steele
----- Original Message -----
From: "Schiza, Apostolia (ISS Atlanta)" <[EMAIL PROTECTED]>
To: "perl-win32-web@listserv. ActiveState. com (E-mail)"
<[EMAIL PROTECTED]>
Sent: Tuesday, January 09, 2001 9:44 PM
Subject: connections between master server and slave servers
> Hi all,
> I have a few IIS servers, from which one acts as a master server and the
> rest as slave servers.
> A web application lives on the master server. A user typically accesses
the
> web application from the master server, and the master server has to
connect
> to one of the slaves to do some work and create results. My problem is,
that
> I cannot find a way of preventing the user of getting a direct connection
> with the slave servers. In other words, I would like the slave server to
> return whatever results (that the web application required from that
server)
> to the master server, and then the user to have the capability of viewing
> the results from the master server only.
>
> I would really really appreciate your help on this (for one more time!)
>
> Thank you!
>
> -Lia-
>
>
>
> _______________________________________________
> Perl-Win32-Web mailing list
> [EMAIL PROTECTED]
> http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
_______________________________________________
Perl-Win32-Web mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
