Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 620
  • Last Modified:

Cisco router IP nat rule entry - configuration failed!

I have a Cisco router which is currently sending all traffic down a VPN connection, we need to remove this and allow internet locally (in fact I have ten sites with a Cisco at each to do this at) on one of the routers if I add the following NAT statement

ip nat inside source list 1 interface Dialer1

I get "Configuration Failed!" - although it appears to have applied.

I can only get to the internet locally on the server at this site, the client PC's cannot.  All of the clients and server are connected to the same switch.  Its not a DNS issue as they cannot even ping. The server however can get to everything as per the other sites

If I remove the NAT rule and allow the clients to connect back to the VPN for internet they start working again.

I have successfully added the NAT rule to the other devices today and they have all worked fine, apart from this one.

I have compared configs and there are no ACL's that are any different.

I disabled the AV on the clients but it made no difference either.

I set one of the clients with a static IP and it also made no difference, then after about 10 mins it started working.  I switched it back to DHCP and it started failing again.  I switched it back to static and nothing.

The only difference from the other devices is the configuration failed! statement

Flat out of ideas....
0
DLeaver
Asked:
DLeaver
  • 2
1 Solution
 
Jan SpringerCommented:
The first thing that you need to do is modify the VPN access list to make only the traffic that should be encrypted "interesting" -- which would be the internal networks of the remote end.

Second, you should be NAT excluding your VPN traffic.

Third, you should have NAT configured on the inside interface.

Fourth, you should specify NAT globally outside.

You don't have a configuration or the version that you are running so I cannot provide snippets.
0
 
DLeaverAuthor Commented:
As soon as I posted it hit me, the ACL 101 for the VPN traffic is still listed with the destination of "any"

I can get on their shortly so I will put it to the test
0
 
DLeaverAuthor Commented:
Thank you - all working now

The extended ACL was the issue - removed and added the IP nat rule and now all the clients are working
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now