Hi, I have a new Cisco ASA 5505 that I can't get internet access on. I set it up using the Startup Wizard. I have my outside interface an address of 22.214.171.124, the T1 provider gave me a router that they have setup with an address of 126.96.36.199, but I can't get to the internet. I can get to the internet if I use my laptop on the Fast Ethernet port on the router, using DHCP on the laptop.
Do I need to set a route outside? I did try this
route outside 0.0.0.0 0.0.0.0 188.8.131.52 0 (this didn't work either)
Yes, You need a "route outside" command. It will not work unless you configure NAT on ASA. You may try to use wizard or CLI for NAT.
I tried those commands and it came back saying it already exists.
Attached is the current config of my Cisco ASA 5505. my usable IP's are 184.108.40.206-246. The WAN IP on the router they provided me is 220.127.116.11. So I though I would make the outside interface (ether0/0) 18.104.22.168.
If anyone can tell me what I'm doing wrong, I would appreciate it.
Your interface ip address should configure like this ip address 22.214.171.124 255.255.255.248 instead. As you mentioned the range is from .241 to 246.
Please also try to configure the default route as
route outside 0.0.0.0 0.0.0.0 126.96.36.199 1
Thanks & Regards,
I have my outside interface set to 188.8.131.52, the router the ISP sent me is set to 184.108.40.206. I can ping the router address of .241 from my Cisco 5505, but clients inside the office can't reach the internet. Makes me believe there is a NAT'ing or route problem.
I'll try "route outside 0.0.0.0 0.0.0.0 220.127.116.11 1 ", because I think I used route outside 0.0.0.0 0.0.0.0 18.104.22.168 0, before (0, instead of a 1 at the end of the command)
I ended up setting the outside interface to DHCP, then set a route to the DHCP address it was given and that worked.
Not sure why it didn't let me just assign the static address and route
Two and a half years later I have the same issue. Internal hosts cannot reach the internet by simply configuring the ASDM wizard (as is claimed in Cisco material) when using a static IP for the internet-facing interface, even after later entering a static route out. Configuring the outside interface to obtain its IP via DHCP during the ASDM Wizard configures internet access for the inside hosts fine. With the static IP configuration I'm able to ping their router from the ASA, but I'll have to allow icmp traffic through to do some more connectivity tests from inside the net. I didn't have much time to configure the device, but will be returning this evening and throughout the week to bring this into production. Configs to follow, but please comment if you're aware of the problem and might know what's wrong with the Cisco wizard's configuration. (only 2 zones - inside and outside)