topic Problems setting up ASA 5505 in Network Security

Problems setting up ASA 5505

spowell5133 — Tue, 12 Mar 2019 06:05:56 GMT

I am new to these things and have been fighting with this ASA for days now. I have tried a lot of the info and guides I saw online to get it working correctly but not much success. My set up is really pretty simple which makes it all the more frustrating. The following is my set up from ISP to ASA.

ISP - 12.X.X.174/30

Cisco Router outside 12.X.X.194 / inside (to ASA) 192.168.0.1 255.255.0.0

After the ASA (inside) is everything else in the network. (DC, Barracuda, switches, APs, etc)

I reset it to factory default to start over.

I have no idea how to make it route correctly for my set up. At one point, I was able to ping google and (as an end user) load the google, yahoo, and youtube websites but nothing else. Now even that isn't working. I don't know what changed. So hopefully someone can, based on the info above, tell me what to change to get it up and running right. Thanks in advance!

Also, I know I am running an old version. I'll deal with that once I get it working.

: Saved
:
ASA Version 7.2(3)
!
hostname ciscoasa
domain-name domain.local
enable password 8Ry2YjIyt7RRXU24 encrypted
names
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address 192.168.0.1 255.255.0.0
!
interface Vlan3
no forward interface Vlan1
nameif dmz
security-level 50
no ip address
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
passwd 2KFQnbNIdI.2KYOU encrypted
ftp mode passive
dns server-group DefaultDNS
domain-name domain.local
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
access-list ACL_OUT extended permit icmp any any
access-list ACL_OUT extended permit udp 192.168.0.0 255.255.0.0 any eq domain
pager lines 24
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu dmz 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-523.bin
no asdm history enable
arp timeout 14400
nat (inside) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 192.168.0.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout uauth 0:05:00 absolute
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!
dhcpd address 192.168.1.2-192.168.1.254 inside
!

!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect icmp
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:b275397802d8c811e7c51c3358f25878
: end
ciscoasa#

hi, since there is a router

viveknathmangalat33 — Sat, 13 Jun 2015 09:42:25 GMT

hi, since there is a router in between asa and isp.

could you check if there is a reverse routing in place to reach your internal network.

Is that is in the router or

spowell5133 — Mon, 15 Jun 2015 14:13:04 GMT

Is that is in the router or the ASA? If its the router, then is should be set correctly because we are simply replacing an old ASA 5505 that died with a new one.

That's what has been the frustrating thing. It seemed like it should have been a simple thing to do... basically a hot swap with maybe a few changes in the ASA settings.

Since I have little experience with setting up switches and firewalls, I was thinking I probably just wasn't entering the correct IPs for the ports into the ASA or some settings to allow traffic from inside to outside. Is it possible the router doesn't see the new ASA because the ASA may have a different IP than the old one did?

I used packet tracer to simulate our set up which of course isn't 100% accurate but I had no problem setting it up in there. Thank you for the response and hopefully any other help you can suggest.

I wanted to update on my

spowell5133 — Mon, 15 Jun 2015 18:41:45 GMT

I wanted to update on my status. After some fiddling, I am now able to ping outside to 8.8.8.8. However, I cannot ping inside and the end user device cannot access the internet or ping the ASA's inside port. Everything up TO the ASA from the end user devices are fine because I have bypassed the ASA while trying to configure it. With that said, I am confident the outside portion of the ASA is correct and I can also say everything between the ASA and the end user devices is good. So logically, it is something to do with my "inside" settings on the ASA.

Again, I thank anyone that can assist. Below is my current "show running configuration"

ciscoasa(config)# sh run
: Saved
:
ASA Version 7.2(3)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
names
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address 192.168.0.250 255.255.0.0
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
passwd 2KFQnbNIdI.2KYOU encrypted
ftp mode passive
dns domain-lookup inside
dns domain-lookup outside
dns server-group DefaultDNS
name-server 8.8.8.8
name-server 4.2.2.2
pager lines 24
logging asdm informational
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
icmp permit any outside
no asdm history enable
arp timeout 14400
global (outside) 1 interface
global (outside) 1 192.168.0.0
nat (inside) 1 192.168.1.0 255.255.255.0 dns
nat (inside) 1 192.168.0.0 255.255.0.0
nat (inside) 1 0.0.0.0 0.0.0.0
nat (inside) 1 192.168.1.0 255.255.255.0 outside
route outside 0.0.0.0 0.0.0.0 12.X.X.174 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout uauth 0:05:00 absolute
http server enable
http 192.168.0.0 255.255.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!