cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4724
Views
5
Helpful
2
Replies

Can't PING to remote router

marianodero
Level 1
Level 1

Hi everyone,

I'm new to subnetting and I'm trying to PING from a PC to a remote router, going through a local router first in a simple topology using Cisco Packet Tracer. So far I've connected and configured the PC and both routers's interfaces, however I don't recieve any package while pinging from the PC to the remote router. In addition, no packet is recieved when pinging from remote router to fastEthernet interface on local router. To make it clear, these are the PINGs that actually work:

-From PC to local router's serial interface

-From PC to local router's fastEthernet interface

-From local router to PC

-From local router to remote router's serial interface

-From remote router to local router's serial interface

And this are the PINGs that didn't work:

-From PC to remote router's serial interface

-From remote router to local router's fastEthernet interface

-From remote router to PC

2 Accepted Solutions

Accepted Solutions

cofee
Level 5
Level 5
It appears remote router doesn't have route to 192.168.1.32/27. The reason you can ping remote router from local router because it's connected to both network and when you ping remote router's serial interface, local router is sourcing from it's serial interface ip address and there it's able to reach it.
If you try pinging remote router's serial interface from local router while sourcing from fast Ethernet interface (192.168.1.33) it won't work because remote router doesn't have a route for that network.
You can create a static route at remote router to solve this issue:
ip route 192.168.1.32 255.255.255.224 192.168.1.133

View solution in original post

Hi

The ping is reciprocal (2 ways), in few words once you have sent an icmp packet to a destination, the destination should know how to send a response back to the source. 

A router will always knows the networks connected directly to itself, so Local router will know the network related to the PC 192.168.1.32/27 and the Point to Point network: 192.168.1.132/30.

The remote router will only know the point to point between itself and local router 192.168.1.132/30 but it doesnt know how to reach the PC so you need to run a dynamic routing protocol like RIP, EIGRP, OSPF between local and remote router to advertise their networks or just use static routing, adding this line on the remote router:

ip route 192.168.1.32 255.255.255.224 192.168.1.133  name ROUTER-LOCAL-LAN

or 

just the PC to be more explicit, using 32 bits. 

ip route 192.168.1.34 255.255.255.255 192.168.1.133  name JUST-PC

Also check if the interfaces are UP and if the PC has an IP gateway configured (192.168.1.33)

Hope it is useful

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

View solution in original post

2 Replies 2

cofee
Level 5
Level 5
It appears remote router doesn't have route to 192.168.1.32/27. The reason you can ping remote router from local router because it's connected to both network and when you ping remote router's serial interface, local router is sourcing from it's serial interface ip address and there it's able to reach it.
If you try pinging remote router's serial interface from local router while sourcing from fast Ethernet interface (192.168.1.33) it won't work because remote router doesn't have a route for that network.
You can create a static route at remote router to solve this issue:
ip route 192.168.1.32 255.255.255.224 192.168.1.133

Hi

The ping is reciprocal (2 ways), in few words once you have sent an icmp packet to a destination, the destination should know how to send a response back to the source. 

A router will always knows the networks connected directly to itself, so Local router will know the network related to the PC 192.168.1.32/27 and the Point to Point network: 192.168.1.132/30.

The remote router will only know the point to point between itself and local router 192.168.1.132/30 but it doesnt know how to reach the PC so you need to run a dynamic routing protocol like RIP, EIGRP, OSPF between local and remote router to advertise their networks or just use static routing, adding this line on the remote router:

ip route 192.168.1.32 255.255.255.224 192.168.1.133  name ROUTER-LOCAL-LAN

or 

just the PC to be more explicit, using 32 bits. 

ip route 192.168.1.34 255.255.255.255 192.168.1.133  name JUST-PC

Also check if the interfaces are UP and if the PC has an IP gateway configured (192.168.1.33)

Hope it is useful

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<
Review Cisco Networking for a $25 gift card