cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2868
Views
0
Helpful
12
Replies

Router Dropping Pings

kevkalu
Level 1
Level 1

Working with 2 Networks:

      NW1 using static IP

      NW2 using DHCP

Pings are successful across LANs but drop between the routers. The routers can ping each other individually, but their networks are inaccessible. 

 

May I please have assistance? 

pass: ccna 

 

 

1 Accepted Solution

Accepted Solutions

There is not 192.168.2.11 on the topology. 

 

We have this IPs on the left:

 

192.168.2.2

192.168.2.3

192.168.2.4

 

We have this IPs on the right:

192.168.1.10

192.168.1.11

192.168.1.12

 

All of them are pinging:

 

C:\>ping 192.168.2.2

 

Pinging 192.168.2.2 with 32 bytes of data:

 

Request timed out.

Reply from 192.168.2.2: bytes=32 time=13ms TTL=126

Reply from 192.168.2.2: bytes=32 time=11ms TTL=126

Reply from 192.168.2.2: bytes=32 time=11ms TTL=126

 

Ping statistics for 192.168.2.2:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 11ms, Maximum = 13ms, Average = 11ms

 

C:\>ping 192.168.2.3

 

Pinging 192.168.2.3 with 32 bytes of data:

 

Request timed out.

Reply from 192.168.2.3: bytes=32 time<1ms TTL=126

Reply from 192.168.2.3: bytes=32 time=10ms TTL=126

Reply from 192.168.2.3: bytes=32 time<1ms TTL=126

 

Ping statistics for 192.168.2.3:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 10ms, Average = 3ms

 

C:\>ping 192.168.2.4

 

Pinging 192.168.2.4 with 32 bytes of data:

 

Request timed out.

Reply from 192.168.2.4: bytes=32 time=23ms TTL=126

Reply from 192.168.2.4: bytes=32 time=11ms TTL=126

Reply from 192.168.2.4: bytes=32 time=11ms TTL=126

 

Ping statistics for 192.168.2.4:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 11ms, Maximum = 23ms, Average = 15ms

 

C:\>

 

what you need to validate once for all:

 

Which ip address the PC have:

ipconfig

 

Which is the gateway ip address

Ping the gatetway

Then, ping the other side.

 

 

View solution in original post

12 Replies 12

Hi

 

 

routing.png

Also,

 Add routes on both router.  Dont forget, remote networks must be informed.

 Or use default routes like this for simplicity 

ip route 0.0.0.0  0.0.0.0  "to R2 IP addresss"

On R2

ip route 0.0.0.0  0.0.0.0 "to R1 IP address"

On R1 

I've enabled IP routing version 1 on both routers with limited success. 

Some requests timeout hinting at faulty routing/switching.

 

PC's are finally able to ping across the network, however, I'm concerned that I can only ping local switches.

 

Switches are unable to ping one another.

Why is this? 

Hi

 Attach the file again and let me look. 

 

The routers are still inaccessible by the opposite LANs. 

 

I had them responding to opposite PC LANs for a time but still could not achieve PC-to-PC pings on opposite LANs.

 

I've added routing land and double-checked the interfaces. 

Hi

 The problem is that on the Router 2, you create a DHCP scope but you did not add default-gateway. This way, the PCs got IP address from DHCP address but they does not have a default gateway.

 

Before:

!

ip dhcp pool network_2

network 192.168.2.0 255.255.255.0

!

!

Now:

 

!

ip dhcp excluded-address 192.168.2.1 192.168.2.10

!

ip dhcp pool network_2

network 192.168.2.0 255.255.255.0

default-router 192.168.2.1

!

 

from PC2.2 to PC1.0

 

C:\>ping 192.168.1.10

 

Pinging 192.168.1.10 with 32 bytes of data:

 

Reply from 192.168.1.10: bytes=32 time<1ms TTL=126

Reply from 192.168.1.10: bytes=32 time=13ms TTL=126

Reply from 192.168.1.10: bytes=32 time=11ms TTL=126

Reply from 192.168.1.10: bytes=32 time<1ms TTL=126

 

Ping statistics for 192.168.1.10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 13ms, Average = 6ms

I've included the default-router input but packets are still dropping. 

Requests are timing out and the PCs disconnect after some testing. 

Alright. I also change something on the router. Let me share with you.

 

ip route 0.0.0.0 0.0.0.0 192.168.3.0

ip route 0.0.0.0 0.0.0.0 192.168.1.0

ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0/0 255

ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0/1 255

!

This routing is not necessary as you already have RIP working.

Enter on this R1 and run:

no ip route 0.0.0.0 0.0.0.0

 

All this routes will desapear and probably your ping will work.

 

all you need is those routes here:

 

R2#sh ip route

Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

* - candidate default, U - per-user static route, o - ODR

P - periodic downloaded static route

 

Gateway of last resort is not set

 

R 192.168.1.0/24 [120/1] via 192.168.3.1, 00:00:10, GigabitEthernet0/0/1

192.168.2.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.2.0/24 is directly connected, GigabitEthernet0/0/0

L 192.168.2.1/32 is directly connected, GigabitEthernet0/0/0

192.168.3.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.3.0/24 is directly connected, GigabitEthernet0/0/1

L 192.168.3.2/32 is directly connected, GigabitEthernet0/0/1

 

R1:

 

R1#sh ip route

Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

* - candidate default, U - per-user static route, o - ODR

P - periodic downloaded static route

 

Gateway of last resort is not set

 

192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.1.0/24 is directly connected, GigabitEthernet0/0/0

L 192.168.1.1/32 is directly connected, GigabitEthernet0/0/0

R 192.168.2.0/24 [120/1] via 192.168.3.2, 00:00:07, GigabitEthernet0/0/1

192.168.3.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.3.0/24 is directly connected, GigabitEthernet0/0/1

L 192.168.3.1/32 is directly connected, GigabitEthernet0/0/1

 

 

- I renewed the IPaddress on LAN 2

- No route on R1

- Established Default-gateway for R2

 

Pings from PC1.11 (Bottom of Right LAN)

 

C:\>ping 192.168.3.2 (R2)

 

Pinging 192.168.3.2 (R2) with 32 bytes of data:

 

Reply from 192.168.3.2: bytes=32 time<1ms TTL=254

Request timed out.

Reply from 192.168.3.2: bytes=32 time<1ms TTL=254

Request timed out.

 

Ping statistics for 192.168.3.2 (PC1.11 to R2):

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

(PC1.11 to PC 2.11)

 

C:\>ping 192.168.2.11

 

Pinging 192.168.2.11 with 32 bytes of data:

 

Reply from 192.168.1.1: Destination host unreachable.

Reply from 192.168.1.1: Destination host unreachable.

Reply from 192.168.1.1: Destination host unreachable.

Reply from 192.168.1.1: Destination host unreachable.

 

Ping statistics for 192.168.2.11:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

C:\>

There is not 192.168.2.11 on the topology. 

 

We have this IPs on the left:

 

192.168.2.2

192.168.2.3

192.168.2.4

 

We have this IPs on the right:

192.168.1.10

192.168.1.11

192.168.1.12

 

All of them are pinging:

 

C:\>ping 192.168.2.2

 

Pinging 192.168.2.2 with 32 bytes of data:

 

Request timed out.

Reply from 192.168.2.2: bytes=32 time=13ms TTL=126

Reply from 192.168.2.2: bytes=32 time=11ms TTL=126

Reply from 192.168.2.2: bytes=32 time=11ms TTL=126

 

Ping statistics for 192.168.2.2:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 11ms, Maximum = 13ms, Average = 11ms

 

C:\>ping 192.168.2.3

 

Pinging 192.168.2.3 with 32 bytes of data:

 

Request timed out.

Reply from 192.168.2.3: bytes=32 time<1ms TTL=126

Reply from 192.168.2.3: bytes=32 time=10ms TTL=126

Reply from 192.168.2.3: bytes=32 time<1ms TTL=126

 

Ping statistics for 192.168.2.3:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 10ms, Average = 3ms

 

C:\>ping 192.168.2.4

 

Pinging 192.168.2.4 with 32 bytes of data:

 

Request timed out.

Reply from 192.168.2.4: bytes=32 time=23ms TTL=126

Reply from 192.168.2.4: bytes=32 time=11ms TTL=126

Reply from 192.168.2.4: bytes=32 time=11ms TTL=126

 

Ping statistics for 192.168.2.4:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 11ms, Maximum = 23ms, Average = 15ms

 

C:\>

 

what you need to validate once for all:

 

Which ip address the PC have:

ipconfig

 

Which is the gateway ip address

Ping the gatetway

Then, ping the other side.

 

 

Hello, I've achieved connectivity.

 

Edits:

1) R2

- Router Rip | Version 2 | Advertise subnet 192.168.2.254 (SW2 for LAN 2) | no auto-summary

- Interface Gi0/1 (LAN 3 Routers) IP Router 0.0.0.0 0.0.0.0 192.168.2.254 (assigning LAN next hop to R1)

- Interface Gi0/0 (LAN 2 Switch)  IP Router 0.0.0.0 0.0.0.0 192.168.3.1     (assigning R1 next hop to SW2/LAN2)

 

*Ping tests achieve 80% on first run but are fix by second run. 

"I've enabled IP routing version 1 on both routers with limited success. "

You mean RIPv1?  If so, as it's a classful routing protocol (as I cannot see [too small diagram] what IPs you might be using in your diagram, so) you might not be following the "rules".  If not, routing won't work correctly.