PDU test and ping test fail in simple network test in packet tracer

[onet12]

Hi,

I am new to packet tracer so please bear with me. I am testing out this simple network, but it seems to fail. I have rip routing enabled, so i'm not sure if i need static routing as well. Thanks!

Configurations:

Pc: 

FastEthernet0 Connection:(default port)

Connection-specific DNS Suffix..:
Physical Address................: 00D0.FF6E.8752
Link-local IPv6 Address.........: FE80::2D0:FFFF:FE6E:8752
IP Address......................: 100.100.100.3
Subnet Mask.....................: 255.0.0.0
Default Gateway.................: 100.100.0.21
DNS Servers.....................: 0.0.0.0
DHCP Servers....................: 0.0.0.0
DHCPv6 Client DUID..............: 00-01-00-01-C2-A4-16-C4-00-D0-FF-6E-87-52

MAster:

GigabitEthernet0/0 100.100.0.21 YES manual up up

GigabitEthernet0/1 10.10.10.40 YES manual up up

Serial0/0/0 unassigned YES unset administratively down down

Serial0/0/1 unassigned YES unset administratively down down

Vlan1 unassigned YES unset administratively down down

Gateway of last resort is 10.10.10.41 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

C 10.0.0.0/8 is directly connected, GigabitEthernet0/1

L 10.10.10.40/32 is directly connected, GigabitEthernet0/1

100.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

C 100.0.0.0/8 is directly connected, GigabitEthernet0/0

L 100.100.0.21/32 is directly connected, GigabitEthernet0/0

S* 0.0.0.0/0 [1/0] via 10.10.10.41

R1

GigabitEthernet0/0 100.100.100.41 YES manual up up

GigabitEthernet0/1 10.10.10.41 YES manual up up

Serial0/0/0 unassigned YES unset administratively down down

Serial0/0/1 unassigned YES unset administratively down down

Vlan1 unassigned YES unset administratively down

Gateway of last resort is 10.10.0.5 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.0.0.0/8 is directly connected, GigabitEthernet0/1
L 10.10.10.41/32 is directly connected, GigabitEthernet0/1
100.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 100.0.0.0/8 is directly connected, GigabitEthernet0/0
L 100.100.100.41/32 is directly connected, GigabitEthernet0/0
S* 0.0.0.0/0 [1/0] via 10.10.0.5
[1/0] via 10.10.10.5

ISP

GigabitEthernet0/0 100.100.100.11 YES manual up up

GigabitEthernet0/1 10.10.10.120 YES manual up up

Serial0/0/0 unassigned YES unset administratively down down

Serial0/0/1 unassigned YES unset administratively down down

Vlan1 unassigned YES unset administratively down down

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.0.0.0/8 is directly connected, GigabitEthernet0/1
L 10.10.10.120/32 is directly connected, GigabitEthernet0/1
100.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 100.0.0.0/8 is directly connected, GigabitEthernet0/0
L 100.100.100.11/32 is directly connected, GigabitEthernet0/0

Server

FastEthernet0 Connection:(default port)

Connection-specific DNS Suffix..:
Physical Address................: 0009.7C65.54CC
Link-local IPv6 Address.........: FE80::209:7CFF:FE65:54CC
IP Address......................: 10.10.10.5
Subnet Mask.....................: 255.0.0.0
Default Gateway.................: 10.10.10.120
DNS Servers.....................: 0.0.0.0
DHCP Servers....................: 0.0.0.0
DHCPv6 Client DUID..............: 00-01-00-01-11-82-67-EA-00-09-7C-65-54-CC

[Martin L]

cannot see topo, pic too small. it's easier if you attach your file here; You can attach your PT file but it must be in a zip format.

Regards, ML
**Please Rate All Helpful Responses **

[onet12]

Hi,

Sorry about that. Here is file

[Martin L · Accepted solution]

Problem is that you have so called dis-contiguous network with 100.100.100.x/8 (100.0.0.0/8) on right of R1 and left as well. Same thing with 10.0.0.0/8 off R1.  it is on both sides;going from left to right we have

100.0.0.0/8 , then 10.0.0.0/8, then  R1 has  10.0.0.0/8 to left and 100.0.0.0/8  to right side. then 100.0.0.0/8 and

10.0.0.0/8 on ISP. 

this created major problems with RIP version 1 which was one of reasons for update of RIP to version 2. also , no auto-summary should help but it does not in your case.

Based on above findings, change networks and keep 100.0.0.0/8 of left of R1 and 10.0.0.0 on right side of R1. perhaps You could also change mask for class A making other class networks.

ip default-gateway 10.10.10.41 is wrong and not needed. also default-information originate does not do anything in your case. 

Regards, ML
**Please Rate All Helpful Responses **

[onet12]

Hi! changing the networks seemed to fix it. Thanks for your help!

[Martin L]

np, btw, not a PT bug.

[Martin L]

TS steps:1 ping default gateway, then trace your destination to see problem.  both end hosts get to default gateway (d.g) routers but not beyond.  next step would be pings/trace from those d.g. routers.  I think that problem seems to be on R1;  its pointing wrong way.  it says to reach PC use GigabitEthernet0/0 - wrong! and vice versa. not sure why yet.

Regards, ML
**Please Rate All Helpful Responses **