cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
697
Views
0
Helpful
4
Replies

Dedicated T1 point to point 1720 router

manish.shah.neo
Level 1
Level 1

We have a point to point tunnel. This was working fine until today afternoon and since then it stopped working I cannot figure out what happened. I can ping the LAN side of other side just fine when I am pinging from within router after telnet to it but I cannot ping it from our LAN of after attaching single computer to FastEthernet0.

After attaching the computer towards FastEthernet0 I can ping the interface FastEthernet0 and I can also ping the interface Serial0?s IP but I cannot ping it to the other side?s interface Serial0.

After I telnet to my router I can ping my side of LAN their side of router and their side of LAN. Any help will greatly be appreciated.

4 Replies 4

omar.ghoneim
Level 1
Level 1

try pinging the other side LAN or serial of the other side router with the source ip of the LAN interface of your router my guess it will not succeed. are you using IPsec/GRE tunneling if so then you might have a problem with the access lists configured on either router. if you could post the configurations of the tunnels on both routers it might help.

Thank you but it started working fine, do not really know what happend. BTW how can I ping using with the source ip of the LAN? NO we are not using IPsec/GRE tunneling.

Hi,

To ping using a soure IP, you should use extended ping:

Corporate#ping

Protocol [ip]:

Target IP address: 192.168.99.1

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y <---

Source address or interface: fastethernet0/0 <---

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.99.1, timeout is 2 seconds:

Packet sent with a source address of 192.168.99.1

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

HTH, please rate all helpful replies,

Mohammed Mahmoud.

aeljabari
Level 1
Level 1

Do one thing more, try to telnet the other end router, and ping your LAN (using the extended ping). if it success that mean you have to review the configuration in your side router and check the access list.

if it fail, i think the problem is on the tunnel. cisco router crached tunnel down. so rebuild your tunnel again.

Regards

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco