jac1991
asked on
Cisco ASA 5505 and Microsoft DHCP superscope
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 ?
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 ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
> Clients get the right IP however Clients
for one subnet or multiple subnets?
> can not communicate between subnets they can ping out to 8.8.8.8 but not google.com
basically it means all subnets can go through their default gateway and reach the Internet at IP layer but DNS resolving got issues.
> 192.168,3.5 can not communicate with anything on 192.168.1.x
even for PING only?
as default gateway is accessible for each subnet, it looks like inter-subnet routing is not enabled on the central router (not a Cisco device? an internet-facing firewall?).
> No router between asa and clients all
switches are cisco L2
it seems to be the reason why subnets can't reach each other as there is no routing between subnets / VLANs. so what's point for you to create VLANs?
BTW, what's the internal IPs for the clients' default gateway?