Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
Unable to ping ip
Hi, If i perform trace I am able to reach my router's wan interface. In ping test I am able to ping interface of ISP facing my router. -
Unable to ping ip
Hi Angmachete, Thanks for reply.. I have nearly 500 locations with this type of configuration. Everything got same config and running fine. Only 1 or 2 locations have this problem. If this is the NAT problem it should occur at every location. Any reply would be appreciated.... -
Unable to ping ip
I am unable to ping my wan ip (172.35.7.246) from remote end. But when I perform trace,telnet,ssh etc it is working fine. No access lists on ISP end or on my router. Below is the config at my end... Bhandari#sh run Building configuration... Current configuration : 2229 bytes ! version 12.4... -
Computer with two NICs
You can probably use "route" command with preference value for network 1.- sannithi
- Post #6
- Forum: Data Transmission general discussion
-
Cisco 1800 Router from PC to WAN not able to ping
what hammnet said is true. If your purpose is to reach only these 2 subets, you can even remove default route also... No need of static routes.. It will follow correct interface based on ip configured .... -
Domain to internal IP conversion
You can perform this by using static nat also . ip nat inside source static <public ip> <port> <private ip> <port no.> extendable.. let me know does it got worked or not...
