Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Nat and telnet issue

I have a quick quesiton....on my edge router I NAT both in and out. Coming in

I have a NAT pool of 170.132.134.0/24. Also my customer has me NATTing my internal server to a nat block of 169.176.124.0/28. So what I have done to test is on my edge router I created a loopback interface with the ip of 170.132.134.58. I have a server of 198.168.8.8 which has a static nat of 169.176.124.4. I don't know if this is a problem or not but when I do a:

telnet 169.176.124.4 /source-interface loopback 0

The telnet hangs from my edge router. Now if I do the same thing but to the real ip address from my end router I can connect:

telnet 198.168.8.8 /source-interface loopback10

Is this something I need to worry about?

I did a ping/traceroute using the NAT 169.176.124.4 and I get responses just when I try to telnet to 169.176.124.4.

By the way that 169.176.124.4 is what the customer sees my 198.168.8.8

Thank you in advance!!!

2 REPLIES
New Member

Re: Nat and telnet issue

Hello

Put ip nat inside on the loop back 0 interface and try.Also make sure that 170.132.134.58 is in the inside NAt pool.

Hope that helps

Ullas

New Member

Re: Nat and telnet issue

Thanks for the advice but that didn't work, maybe I'm explaining it wrong. I'm just doing this as a pretest for Sundays real test. I didn't want to wait till then to find out its now working. anyways sourcing from loopback10 I can ping and traceroute to 169.176.124.4 but not telnet. I do a traceroute using the real ip 198.168.8.8 and the NAT IP of 169.176.124.4 and both take the same path and end up at the same place. The 169.176.124.4 is what the customer will see my server as not the 198.168.8.8.

157
Views
0
Helpful
2
Replies