HI.
> Yizhar has a typo in his fromdmz access list, 10.1.10.13
> and 10.1.10.15 should be 10.1.10.3 and 10.1.10.5
Nope. It's not a typo.
The idea is to use some address, which will not overlap and must not match an address of a real server in the DMZ.
However it conflicts with this:
> global (DMZ) 1 10.1.10.8-10.1.10.14
So you should change either the global (dmz) or the static (inside,dmz) so that nothing overlaps or conflicts.
I suggest that the global (dmz) statement will use only a single IP address (PAT). This is for internal hosts accessing the web servers:
> global (DMZ) 1 10.1.10.8
Or any other unused address in 10.1.10.X
The static(inside,dmz) statements will allow (in conjunction with proper access-list) the web servers to access internatl SQL servers.
The web servers will need to be configured to look for the SQL servers using the same ip address sepcified in the static mapping.
You can also use static with the same ip address, like this:
static (inside,dmz) 192.168.10.3 192.168.10.3
static (inside,dmz) 192.168.10.5 192.168.10.5
In that case the webserver will look for the SQL server using their internal ip address 192.168.10.X
After each change of nat,global,static commands, you should issue at the pix:
clear xlate
Here is a modified config from my previous post:
global (outside) 1 209.0.0.203
global (DMZ) 1 10.1.10.8
nat (inside) 1 192.168.10.0 255.255.255.0
static (dmz,outside) 209.xx.xx.200 10.1.10.3
static (dmz,outside) 209.xx.xx.225 10.1.10.5
static (dmz,outside) 209.xx.xx.226 10.1.10.6
static (inside,dmz) 192.168.10.3 192.168.10.3
static (inside,dmz) 192.168.10.5 192.168.10.5
access-list fromoutside permit tcp any 10.1.10.0 255.255.255.0 eq 80
access-list fromoutside permit tcp any 10.1.10.0 255.255.255.0 eq 443
access-group fromoutside in interface outside
access-list fromdmz permit tcp any host 192.168.10.3 eq 1433
access-list fromdmz permit tcp any host 192.168.10.5 eq 1433
access-list fromdmz deny ip any 192.168.10.0 255.255.255.0
access-list fromdmz permit ip any any
access-group fromdmz in interface dmz
> FYI,I am a router guy, not a PIX guy ...
Tip1: remember that pix uses subnet mask in access-list unlike IOS which uses "wildcard".
Tip2: Use access-list only and not the obsolute conduit command.
Tip3: Start new configuration from scratch, to eliminate left overs.
Bye
Yizhar Hurwitz