cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
36763
Views
0
Helpful
13
Replies

Failed ping from PC1 to PC3 (Packet Tracer)

I'm doing a practice from the "CCNA Exploration 4.0: Accessing the WAN Student Packet Tracer Manual" (PT Activity 2.1.7: Troubleshooting a Serial Interface). I made the topology according to the image and set the IP addresses on the correct interfaces. Almost, I put the serial cable (Router2 to Router3) in the correct serial port (0/0/1 - 0/0/1).

By default, Packet Tracer sets all the routers with HDLC encapsulation.

When I try to make a ping from PC1 to PC3, I can't. I checked all my topology and I don't found the problem.

I attached and imagen and my .pkt project.

Test.JPG

Sorry for my bad english, the project name, and the question, but I'm new using this discussion forum. Thank you for all.

1 Accepted Solution

Accepted Solutions

Hi Armando,

Jon is right.

Here are the exact commands you need to add:

R1(config)#ip route 192.168.30.0 255.255.255.0 10.1.1.2

R2(config)#ip route 192.168.30.0 255.255.255.0 10.2.2.2

R2(config)#ip route 192.168.10.0 255.255.255.0 10.1.1.1

R3(config)#ip route 192.168.10.0 255.255.255.0 10.2.2.1

Best regards,

Jan

View solution in original post

13 Replies 13

Jan Hrnko
Level 4
Level 4

Hi Armando,

no need to apologise . We would most certainly like to help you, however you did not include the .pkt file in the post. Please, try to upload it again.

Best regards,

Jan

The Packet Tracer project:

http://www.4shared.com/file/XS4cSucn/Hola.html

Thank you for all.

Hi Armando,

When troubleshooting, you should use traceroute (tracert 192.168.30.10 command) on PC1. Traceroute basically tells you how far did the packet make it. In your case, packet doesn't pass R1 so you should check R1 first.

After issuing show ip route command on R1, it is clear that it don't have any route for network 192.168.30.0/24. That's because you haven't configured either static or dynamic routing.

Solutions:

  • 1 configure static routes on appropriate routers (R1,R2,R3)
  • OR
  • 2 configure dynamic routing protocols (such as RIP,EIGRP,OSPF...)

If you need any assistance with that or if you have more questions, please, feel free to ask!

Best regards,

Jan

How can I do to configure static routes on R1-R2-R3, and making this changes I can make ping from PC1 to PC3?

I can't read PT files but i can give you an example -

H1 -> (192.168.5.1/24 - fa0/0) R1 (s0/0 - 192.168.6.1/30) -> (192.168.6.2/30 - s0/0) R2 (fa0/0 - 192.168.7.1/24) -> H2

to be able to ping from H1 to H2 you would need to add these commands in config mode on R1 and R2 -

R1

==

ip route 192.168.7.0 255.255.255.0  192.168.6.2   <--  now R1 now how to get to the 192.168.7.0/24 network

R2

==

ip route 192.168.5.0 255.255.255.0 192.168.6.1  <--  now R2 knows how to get to the 192.168.5.0/24 network

So in your example you need to -

1)  On R1 add a static route for the PC3 network pointing to R2

2)  On R2 -

a) add a static route for the PC1 network pointing to R1

b) add a static route for the PC3 network pointing to R3

3) on R3 add a static route for the PC1 network pointing to R2

Jon

What are the arguments of the ip route?

Armando

ip route  

Jon

Hi Armando,

What are the arguments of the ip route?

  • Router(config)#ip route DESTINATION_NETWORK MASK NEXTHOP_IP

or

  • Router(config)#ip route DESTINATION_NETWORK MASK OUTBOUND_INTERFACE

Or the 3rd way that you can't use in PT, but I think is the best:

Router(config)#ip route NETWORK MASK OUTBOUND_INTERFACE NEXTHOP_IP

It does not really matter if you use next hop ip or outbound interface in your case, but it would matter if the interface was not point to point serial. If the routers were connected through some multipoint connection, like ethernet, I would highly discourage you to state just the outbound interface name.

Best regards,

Jan

Hi Armando,

Jon is right.

Here are the exact commands you need to add:

R1(config)#ip route 192.168.30.0 255.255.255.0 10.1.1.2

R2(config)#ip route 192.168.30.0 255.255.255.0 10.2.2.2

R2(config)#ip route 192.168.10.0 255.255.255.0 10.1.1.1

R3(config)#ip route 192.168.10.0 255.255.255.0 10.2.2.1

Best regards,

Jan

Thank you, Jan. I solved my problem in this practice. Sorry for the inconvenient.

Hi Armando,

I am happy to hear that you resolved the problem. No need to aplogise! Please, mark the question answered, if you can. Take care!

Best regards,

Jan

Why in the fourth block of the ip address and subnet mask (command ip route) puts .0?

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