ASA inter vlan routing

galaga5656 — Tue, 12 Mar 2019 05:33:40 GMT

Hello Question, I have an ASA 5505 with one vlan. I have created a DHCP superscope on our Microsoft server 192.168.1.0 192.168.3.254 Clients get the right IP however Clients can not communicate between subnets they can ping out to 8.8.8.8 but not google.com 192.168,3.5 can not communicate with anything on 192.168.1.x No router between asa and clients all switches are cisco L2 Anyway to overcome this ? Create vlan 2 with 192.168.3.0/24 on switches and asa ?

if they can ping by IP but

cpgsystems — Fri, 27 Feb 2015 13:56:53 GMT

if they can ping by IP but not by name, then the issue is DNS, not firewall. If the DNS translation request cannot get past the firewall, then it will fail. The fact that pinging by IP works shows that the ACL and NAT are setup correctly for ping at least. Now you just need to identify if the same areas are configured for dns resolution

RE: 192.168,3.5 can not communicate with anything on 192.168.1.x

This sounds like a netmask problem too. 255.255.252.0 yes? Your network actually has a bunch more IP's than you intended, I guess

Address:   192.168.1.0
Netmask:   255.255.252.0 = 22
Wildcard:  0.0.3.255
=>
Network:   192.168.0.0/22
Broadcast: 192.168.3.255        
HostMin:   192.168.0.1           
HostMax:   192.168.3.254         
Hosts/Net: 1022

Does everything have the correct netmask and gateway information? Can you post an IPconfig /all from a .3 workstation AND post the ASA's config please?

topic ASA inter vlan routing in Network Security

ASA inter vlan routing

if they can ping by IP but