Everyone,
We have a Windows 2003 IIS 6 deployment of (3) servers load balanced
via a Cisco Content Switch 11503 which we also use the SSL module on
the CSS to take this load off the servers as well. We have a DMZ
defined for our WWW servers as well as a DMZ defined for our SQL
servers as well. Each of these are separate interfaces off our PIX.
The question is handling RPC calls between the www servers and the SQL
servers. As I understand by default RPC allocates between ports
1024-5000 and our network engineering staff does not like having that
many ports open between the (2) segments of the network.
So, we have RPC calls initiating both ways (from www to sql and from
sql to www) and they want the best way to secure this and limit the
ports. I have read numerous MS articles on registry hacks, allocating
ports but I cannot run across anything that everyone is comfortable
with.
Does anyone have any best practices or ideas they have come up with? I
have read the article on configuring RPC to use certain ports and how
to help sercure those ports via IPSec and feel this could be deployed.
Has anyone deployed RPC via HTTP?
Thanks for any help on this.
-WE