Basic config problm =(
Dubuku57
Member Posts: 81 ■■□□□□□□□□
in CCNA & CCENT
Hi all,
I think this is uber basic but am not able to ping the Host B. This is what i set up..
Host A --> Router A Fa0/0
RouterA S0/0 --> Router B S0/0 (I created a static route here and clock rate is set)
Router B Fa0/0 --> Host B
Host A : 192.168.101.2
RouterA Fa0/0 : 192.168.101.1
RouterA S0/0 : 192.168.1.1
RouterB S0/0 : 192.168.1.2
RouterB F0/0 : 192.168.100.1
Host B : 192.168.100.2
Router A can ping Host B but Host A cant!! Why is this so? Can someone pls help me out here? Feeling like a Dingbat..sigh...
I think this is uber basic but am not able to ping the Host B. This is what i set up..
Host A --> Router A Fa0/0
RouterA S0/0 --> Router B S0/0 (I created a static route here and clock rate is set)
Router B Fa0/0 --> Host B
Host A : 192.168.101.2
RouterA Fa0/0 : 192.168.101.1
RouterA S0/0 : 192.168.1.1
RouterB S0/0 : 192.168.1.2
RouterB F0/0 : 192.168.100.1
Host B : 192.168.100.2
Router A can ping Host B but Host A cant!! Why is this so? Can someone pls help me out here? Feeling like a Dingbat..sigh...
Comments
-
Dubuku57 Member Posts: 81 ■■□□□□□□□□The default on Host A is 192.168.101.1...There is no firewall setup...its a simulation in Packet Tracer...I included routing -- Router Rip on routerA
network 192.168.101.0
network 192.168.1.0
and Router rip on routerB
network 192.168.1.0
network 192.168.100.0
Then i was able to ping Host B..But i dont understand why a static route is not sufficient? -
billyr Member Posts: 186Remember routers only know about directly connected networks.
If not using a routing protocol, then router A will need a static route telling it how to reach the 192.168.100.0 network.
Router B will then need to know how to reach the 192.168.101.0 network. -
Neeko Member Posts: 170The default on Host A is 192.168.101.1...There is no firewall setup...its a simulation in Packet Tracer...I included routing -- Router Rip on routerA
network 192.168.101.0
network 192.168.1.0
and Router rip on routerB
network 192.168.1.0
network 192.168.100.0
Then i was able to ping Host B..But i dont understand why a static route is not sufficient?
Did you have a static route on router B? If not, it wouldn't have known how to route the packets back to 192.168.101.0. That's why with RIP enabled on both routers, it worked fine, because both routers knew about both each other's networks. -
Dubuku57 Member Posts: 81 ■■□□□□□□□□No i hadnt put a Static route on RouterB. So in this case,
1. Host A could not ping because there was no Static route back to it on Router B. 2. 2. But Rip worked because Router A was advertising Host A's network.
So from now, for any network, i must have static routes on the router connecting to the lan segments of the adjacent router. Router A and B could ping each other and rouiter A could ping Host B perfectly fine because they are directly connected.
Correct? -
jscimeca715 Member Posts: 280No i hadnt put a Static route on RouterB. So in this case,
1. Host A could not ping because there was no Static route back to it on Router B. 2. 2. But Rip worked because Router A was advertising Host A's network.
So from now, for any network, i must have static routes on the router connecting to the lan segments of the adjacent router. Router A and B could ping each other and rouiter A could ping Host B perfectly fine because they are directly connected.
Correct?
That should work. Although I would imagine the routing protocol would be preferred in most real world cases. Static routes leave a lot of room for error in syntax and stuff. -
Dubuku57 Member Posts: 81 ■■□□□□□□□□Ogi, thanksuu! Im gonna try this lab few more times again to make sure. Hopefully wont run into similar problems..Argh..stress...