09-12-2005 02:17 AM - edited 03-05-2019 11:38 AM
Sorry for bothering with such silly question but in never really happened to me to do something like this so I ask your help.
So: i need to create a static NAT entry so that the outside, say, TCP/9000 would be statically NATted to, say, 192.168.1.15 TCP/8000. So, I thought it was the same old story:
ip nat inside source static tcp 192.168.1.15 8000 interface atm0.1 9000
Well, I'm probably missing something but this thing doesn't seem to work.
Thanks in advance for your assistence
09-12-2005 03:26 AM
hi
is it possible for you to change the statement from interface atm0.1 to the ip address being assigned to that interface ?
if it doesnt help u out can u check out after using the extendable keyword in addition to the command syntax ?
regds
09-12-2005 09:19 AM
Thank you for your answer. Unluckly, I can't use the ip address but it shouldn't make any difference, as far as I know.
I tried to catch the meaning of the extendable keyword searching cisco.com and what I found is:
The extendable keyword allows the user to configure several ambiguous static translations, where an ambiguous translations are translations with the same local or global address.
Which is not our case
09-12-2005 08:06 PM
hi
from my personal exp we did face similar kinda probs quite sometime back we got rid of the same by mapping that to the ip instead of the interface thats the reason for suggesting you to try the same.
regds
09-15-2005 06:11 AM
So I'll have to find another way since in my case, the wan ip is dynamic.
Thank you anyway!
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