cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
474
Views
1
Helpful
5
Replies

Can ping switches on different subnets but not the devices attached

I'm working through a lab and I'm assuming i missing something obvious. I can ping switch0 from Router 1 but not server0. Same with R2 I can ping switch1 but neither hosts.

Any help appreciated I'm just banging my head against a wallPicture1.png

1 Accepted Solution

Accepted Solutions

M02@rt37
VIP
VIP

@streetteamcollective 

Attached your file with corrections.

Please, check all platforms (Switches/Routers) and verify on your initial lab what is the problems:

- static routing issues

- nat issues

- eigrp issue

- Router On A Stick issues (Server0 side)

 

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

View solution in original post

5 Replies 5

M02@rt37
VIP
VIP

Hello @streetteamcollective 

First if you check Gateway reachability from Hosts and Servers, you can see that there is an issue on LANs side.

M02rt37_0-1744834876226.png

The problem is the configuration on Router's interface facin the Swithes.

You need sub-interface, called Router On A Stick configuration: https://www.ciscopress.com/articles/article.asp?p=3089357&seqNum=5

->You should have something like that:

M02rt37_1-1744835321123.png

After that, Host-1R-B can ping its Gateway:

M02rt37_2-1744835390362.png

Check ip routing on routers, NAT and Standby (hsrp) IP... this VIP should be the Gateway of Servers. 0-RB...

I let you finish this lab.

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

My main concern is the ability for anything connected to R1 to ping R2 or anything connected to it. I know theres something wrong between R1 and R2 but I cannot figure it out. I think the ip routes are good but clearly i'm missing something.

I did put the router on a stick configuration on R1and R2  but still can't ping past R1 or R2 on either side.

Hello @streetteamcollective 

Check ip routing on routers, NAT and Standby (hsrp) IP... this VIP should be the Gateway of Servers. 0-RB...

Start by debugging each LAN side. After each hosts ping their Gateway, start debugging routing step by step, hop by hop.

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Martin L
VIP
VIP

First, I see wrong default gateway on left side for both PCs and switch; fixing that PCs are ok but not switch1 which cannot ping R2. Routers know about their connected networks so 2 static routes on R1 are not needed.

R1 has also static NAT 192.168.6.11 182.0.0.2 - not sure why or what for?

R2 on right side complains about neighbor EIGRP

%DUAL-5-NBRCHANGE: IP-EIGRP 375: Neighbor 144.2.0.10 (FastEthernet1/0) is up: new adjacency

%DUAL-5-NBRCHANGE: IP-EIGRP 375: Neighbor 144.1.0.10 (FastEthernet0/1) is down: Interface Goodbye received

....that's what I found so far, will add more if time permits

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

M02@rt37
VIP
VIP

@streetteamcollective 

Attached your file with corrections.

Please, check all platforms (Switches/Routers) and verify on your initial lab what is the problems:

- static routing issues

- nat issues

- eigrp issue

- Router On A Stick issues (Server0 side)

 

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.