DLeaver
asked on
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....
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....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
The extended ACL was the issue - removed and added the IP nat rule and now all the clients are working
ASKER
I can get on their shortly so I will put it to the test