in our network, we are using a public IP address range for our NAT solution rather than using the more common private address range. the problem is that, from out side the NAT domain, we can't connect to a machine in that nat domain even though we can ping it. it is understandable why this would be if we were using a private address range but we couldn't figure out why we can't establish a connection when using private addresses with NAT.
check if there are redundant return paths from the host that you are trying to reach back to the source that initiates the TELNET traffic. If there are redundant paths, make sure the interfaces are all configured with the IP NAT OUTSIDE command.
There is a little flash animation which shows you why PING would work in such a scenario, but TELNET would not:
(NAT) Flash Animation Case Study: Can Ping Host, but Can't Telnet
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.