cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
305
Views
0
Helpful
1
Replies

Static NAT creating problem

young.andrew
Level 1
Level 1

i created a static nat on my cisco 2801 using the following command:

ip nat inside source static 10.10.5.114 <public ip> extendable

The nat works. I able to get to the machine from outside the internet. I also added several ACl's which filter the traffic to that NAT only on port 80, 8080, and 443.

Users can also VPN into the router. Once i VPN in, i recieve a local ip of 192.168.0.X. I have other servers on the same internal subnet of (10.10.5.x).

For some reason, after creating this nat, i can no longer remote desktop to 10.10.5.114. I am still able to remote desktop to servers on the 10.10.5.X subnet.

I believe its my static nat causing the problem. When i vpn it, tried to ping the server 10.10.5.115, it resolves to

10.10.5.115. But when i ping 10.10.5.114, it resolves to the <public ip>.

In the last line of my acl i have:

access-list 100 deny ip any any log

to see what was getting denied. To no suprise, i can see packets from my ISP's static WAN IP trying to establish a RDP with <public ip> instead of my VPN ip of 192.168.0.X.

Any ideas on how to fix this so that vpn users are not resolving to the <public ip> of this nat setup? thanks.

1 Reply 1

Hello Andrew,

can you post the configuration of your router ? When you say that you can successfully ping 10.10.5.115, is that from the outside (public) Internet ?

Regards,

GP

Review Cisco Networking for a $25 gift card