Configuring Cisco ASA 5520 with two T1 interfaces

We are trying to seperate traffic on our network. We have a T3 on our main network for Internet traffic and we added another T1 for our Ecommerce server. Our main network is 192.168.100.0 (Inside) and we want to use 10.30.30.0 (DMZ-Inside) for our Ecommerce network, and would like to be able to access Ecommerce from our main network. We are setup on Ecommerce to see the server from a public IP, but we cannot see it internally. Suggestions?
jgonzAsked:
Who is Participating?
 
wilsjConnect With a Mentor Commented:
if you have a global and nat entry for the dmz then all you need is an ACL allowing the traffic from the dmz interface to the inside interface. Something like this should work.

global (dmz) 1 interface
nat (dmz) 1 0.0.0.0 0.0.0.0

access-list dmz_in permit tcp host 10.30.30.x eq www any
access-group dmz_in in interface dmz

0
 
jgonzAuthor Commented:
We figured we would need an access list, but we have four interfaces - two Outside (T3 and T1) and two Inside:
Outside - 70.251.X.X
DMZ - 12.234.X.X
Inside - 192.168.100.0
DMZ-Inside 0 10.30.30.0
0
 
jgonzAuthor Commented:
Correction:

We figured we would need an access list, but we have four interfaces - two Outside (T3 and T1) and two Inside:
Outside - 70.251.X.X (public IP)
DMZ - 12.234.X.X (public IP)
Inside - 192.168.100.0
DMZ-Inside - 10.30.30.0
0
 
wilsjCommented:
When you can. Could you post the info directly from your ASA. I would like to see the security on the dmz-inside interface and your nat, global and static statements for the dmz-inside.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.