Also can you do a show route command and post that as well please?
Main Topics
Browse All TopicsI have a Cisco ASA 5505 with the necessary licensing and capabilities of multiple VLANS and I am trying to use it to route two different networks. I have the VLAN setup up and have set the security level set to 100 (same as the internal network) and have selected the option to route within same security networks. The two networks (192.168.10.0/24 and 192.168.50.0/24) are not talking to each other (can't ping between them) so I need some help getting this working. In addition there are two hosts on each of the two networks that I am trying to route that cannot talk to each other so I need some help configuring the access-lists. Every time I try to insert a rule, it shuts off internet access to the entire organization. Config is posted in the code segment.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yes hosts on VLAN1 can ping 192.168.10.1 and hosts on VLAN23 can ping 129.168.50.253.
Gateway of last resort is 209.161.27.45 to network 0.0.0.0
C 192.168.10.0 255.255.255.0 is directly connected, inside
C 209.161.27.44 255.255.255.252 is directly connected, outside
C 127.1.0.0 255.255.0.0 is directly connected, _internal_loopback
S 192.168.5.3 255.255.255.255 [1/0] via 209.161.27.45, outside
C 192.168.50.0 255.255.255.0 is directly connected, MOZART
S* 0.0.0.0 0.0.0.0 [1/0] via 209.161.27.45, outside
You went through all that to get the two VLANs communicating and now want to remove that ability....?
NAT for that VLAN is easy:
Create a No-NAT ACL for stuff we don't want translated:
access-list mozart_nat0_outbound remark ** No-NAT ACL for VLAN23 **
nat (MOZART) 0 access-list mozart_nat0_outbound
nat (MOZART) 1 0.0.0.0 0.0.0.0
Remove the same security handling:
no same-security-traffic permit inter-interface
no same-security-traffic permit intra-interface
An ACL for the interface:
access-list mozart_access_in remark ** Access control for VLAN 23**
access-list mozart_access_in deny ip any 192.168.10.0 255.255.255.0
Apply the ACL:
access-group mozart_access_in in interface MOZART
Note that the name references I have (MOZART) is from the nameif command at the interface level. If you change the interface name you need to update all applicable rules.
Ahhh just one host on each network. Use this ACL, assuming your AD servers are 192.168.10.100 and 50.100 respectively:
access-list mozart_access_in remark ** Access control for VLAN 23**
access-list mozart_access_in deny ip host 192.168.50.100 host 192.168.10.100
access-list inside_access_in remark ** Access control for VLAN 1**
access-list inside_access_in deny ip host 192.168.10.100 host 192.168.50.100
Be sure you read over the ACL so you understand how it works, not just copy and paste it in.
I have entered the nat rules and I am still able to ping from one server to the other. Here is what I have for the rules. Since the server on the 192.168.50 network has 3 IP addresses assigned I had to write some additional rules. What do I have wrong?
access-list mozart_access_in extended deny ip host 192.168.50.5 host 192.168.10.9
access-list mozart_access_in extended deny ip host 192.168.50.7 host 192.168.10.9
access-list mozart_access_in extended deny ip host 192.168.50.8 host 192.168.10.9
access-list inside_access_in extended deny ip host 192.168.10.9 host 192.168.50.5
access-list inside_access_in extended deny ip host 192.168.10.9 host 192.168.50.7
access-list inside_access_in extended deny ip host 192.168.10.9 host 192.168.50.8
Business Accounts
Answer for Membership
by: StrifeJesterPosted on 2009-08-18 at 13:26:45ID: 25127299
Can a machine in VLAN 1 ping 192.168.10.1?
Can a machine in VLAN 23 ping 192.168.50.253?
While you try this i am going to go over the ACLs and see if there is anything there that i can see.