Solved

Cisco ASA Firewall settings

Posted on 2011-09-27
7
426 Views
Last Modified: 2012-05-12
My environment has two separate domains, with a Cisco ASA 5520 acting as Firewall/router in between the 2 domains, and between them and the internet.

Domain A uses the "Inside" interface and has 3 domain controllers
DCA1  192.168.1.1
DCA2  192.168.1.2
DCA3  192.168.1.3

Domain B uses the "Public" interface and has 2 domain controllers
DCB1  192.168.2.1
DCB2  192.168.2.2

I need to set up domain trust between the domain controllers in the 2 domains.

Right now, All domain controllers on domain A can ping all DC's on domain B.
NO domain controllers on domain B can ping any DC's on domain A.

What access rules do I need to configure on the ASA to allow DCB1 and DCB2 access to DCA1, DCA2 & DCA3, while blocking any other traffic from domain B to domain A?

I would appreciate some assistance, as right now all traffic from B to A is blocked and I cannot create the trust.
0
Comment
Question by:Andrea_
7 Comments
 
LVL 33

Assisted Solution

by:MikeKane
MikeKane earned 150 total points
ID: 36711668
Not an optimal setup from a networking standpoint.    The ASA uses 2 zones like this for security where inside is trusted and outside is not trusted.     In order to get device on the outside to speak with devices on the inside, you need to create a Static NAT from outside to inside, create an access-list to allow the traffic, and finally apply that ACL to an interface.  

Something like this:


static (inside, outside) 192.168.1.1 192.168.1.1 netmask 255.255.255.255
static (inside, outside) 192.168.1.2 192.168.1.2 netmask 255.255.255.255
static (inside, outside) 192.168.1.3 192.168.1.3 netmask 255.255.255.255

access-list outside_in extended permit ip 192.168.2.0 255.255.255.0 host 192.168.1.1
access-list outside_in extended permit ip 192.168.2.0 255.255.255.0 host 192.168.1.2
access-list outside_in extended permit ip 192.168.2.0 255.255.255.0 host 192.168.1.3

access-group outside_in in interface outside

0
 
LVL 1

Author Comment

by:Andrea_
ID: 36711760
Sorry, I left out some key information.  
Both of those interfaces are on the inside.
The ASA actually has 5 interfaces configured (1 outside, 4 inside):
*** Outside  (198.111.167.xxx)
Inside  (192.168.255.1)
Public  (192.168.2.1)
Publicwlan (192.168.4.1)
Management (192.168.1.1)

Am I correct that the rules would be different since these interfaces are both internal?
0
 
LVL 1

Author Comment

by:Andrea_
ID: 36713736
Can anyone help me?  I really need to get these domain controllers talking to each other!
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
LVL 79

Accepted Solution

by:
lrmoore earned 200 total points
ID: 36713950
What are the security levels of the 2 interfaces?
1st, make them the same
2nd, check the box to allow same-security traffic inter-interface
3rd, create a network static
static (Inside,Public) 192.168.255.0 192.168.255.0 netmask 255.255.255.0
4th, create an access-list
access-list Public-Inside permit ip 192.168.2.0 255.255.255.0 192.168.255.0 255.255.255.0
5th, apply the acl to the Public interface
access-group Public-Inside in interface Public
0
 
LVL 1

Author Comment

by:Andrea_
ID: 36714001
I want to make sure I understand your directions.  
Step 3, is that creating a static NAT?  or is there another type of static network I should be configuring?
0
 
LVL 18

Assisted Solution

by:fgasimzade
fgasimzade earned 150 total points
ID: 36715781
Well, if security level is the same you would not need static NAT. Just make security levels the same and issue same-security traffic inter-interface - this will allow communication from one LAN to another.
0
 
LVL 1

Author Comment

by:Andrea_
ID: 36717663
Thanks to all of you for your help.  
My solution ended up being this:
In the ASDM console:
Configuration- Firewall- Public Servers-
inside 192.168.1.1 ip public 192.168.1.1
inside 192.168.1.2 ip public 192.168.1.2
inside 192.168.1.3 ip public 192.168.1.3

That allowed my domain B servers to find my domain A servers, so that my access rules would work.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
cisco 2800 cannot ping lan 4 23
Cisco 800 router unable to connect through TPG network 12 23
Cisco IPSec VPN Connection with Mac only sees Public folder 19 31
Cisco WRVS4400N 11 37
Have you experienced traffic destined through a Cisco ASA firewall disappears and you do not know if the traffic stops in the firewall or somewhere else? The solution is the capture feature. This feature was released in 6.2(1) and works in all firew…
Concerto Cloud Services, a provider of fully managed private, public and hybrid cloud solutions, announced today it was named to the 20 Coolest Cloud Infrastructure Vendors Of The 2017 Cloud  (http://www.concertocloud.com/about/in-the-news/2017/02/0…
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…
Both in life and business – not all partnerships are created equal. Spend 30 short minutes with us to learn:   • Key questions to ask when considering a partnership to accelerate your business into the cloud • Pitfalls and mistakes other partners…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question