01-03-2013 03:28 AM - edited 03-04-2019 06:33 PM
I've having a problem with our company ASA5505 router.
We recently moved to a new adress, so everything had to be set up again. I have a static IP, submask and gateway from our new ISP. The router have been factory reset before moving. We have betweeen 10-20 employees on our LAN in the office. In an attempt to make things easier I have changed the internal IP (and IP range) to 10.0.200.1 with a range from 10.0.200.5 - 10.0.200.100 as our NAS/printer/plotter have IPs within this range.
I can ping machines on the internal IPs and in ASDM the Outside interface is show as "up" with a green arrow. But there still isn't any internet connection. The only thing I haven't tried (because people need the current network to be online) is changing
"route inside 0.0.0.0 0.0.0.0 62.242.X.X 1" to "route outside 0.0.0.0 0.0.0.0 62.242.X.X 1"
Can you guys see if anything else should be changed for this to work? I have recieved a primary and secondary DNS adress as well, but I'm in doubt as to were I'm supposed to enter these (Using ASDM Version 6.3). I would like everything "Behind" the router to be run by DHCP.
Here is the running config:
ASA Version 8.2(2)
!
hostname ciscoasa
enable password X
passwd X
names
!
interface Vlan1
nameif inside
security-level 100
ip address 10.0.200.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address 62.242.X.X 255.255.255.252
!
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
!
ftp mode passive
dns domain-lookup inside
pager lines 24
logging asdm informational
mtu inside 1500
mtu outside 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
route inside 0.0.0.0 0.0.0.0 62.242.X.X 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 sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 10.0.200.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd dns 194.239.X.X 193.162.X.X
dhcpd auto_config outside
!
dhcpd address 10.0.200.5-10.0.200.100 inside
dhcpd dns 194.239.X.X 193.162.X.X interface inside
dhcpd enable inside
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
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 ip-options
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:28ad57e19743b0f3ca5b728c6ac89c23
: end
01-03-2013 03:45 AM
Dennis,
Try to ping the gateway from the ASA. If that's successful, try to ping 4.2.2.1 from a workstation. If that works, then it's a dns issue somewhere. If it does not work, it's a nat issue. If you can't ping it from the ASA, make sure that the new ISP has bridged the modem/router that they provide. I'm assuming this is a cable/dsl connection, and if that's the case I'm leaning toward the modem/router not being bridged.
HTH,
John
*** Please rate all useful posts ***
01-03-2013 03:58 AM
Hi John.
Thank you for that checklist! I will have to wait untill after hours to test it though. The connection is actual a fiber. It's a dualfiber cable being converted by a Raycore box with only a RJ45 output named "LAN". I assume, maybe incorrectly, that this box only converts the signal. This would make the 5505 the only router connected. Image attached below.
Thank you,
Dennis
01-03-2013 06:12 AM
Ok, so now I tried setting up an outside route with the provided gateway adress. I still can't ping outside from my machine, that is, untill I change the DNS on my own machine. Suddenly I got internet along with NAS/printer and so on.
So my problem is getting the 5505 to supply my machines a DNS adress automaticly. Any tips as to where the correct place for the DNS adress is?
Thanks,
Dennis
01-03-2013 06:31 AM
Ok, got everything working now.
Under Configuration -> Device management -> DNS - > DNS Client. Here I configured the DNS setup as one group and under DNS lookup I enabled DNS for the inside interface and added the primary and secondary DNS fra my ISP. Voilá, internet and network funktioning.
Thought I would add the solution for anyone stumbeling over this post later on. Now I just need to setup VPN for the first time ever :S
Dennis
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide